Re: avoid mktemp/mkstemp internally

2016-05-19 Thread Mike Frysinger
On 19 May 2016 14:37, Chet Ramey wrote: > On 5/16/16 10:36 AM, Mike Frysinger wrote: > >> Because many traditional implementations of mktemp/mkstemp suck. > > > > and many modern implementations work perfectly fine. why is the default > > to penalize good/fixed versions ? how about we flip this

Re: avoid mktemp/mkstemp internally

2016-05-19 Thread Chet Ramey
On 5/16/16 10:36 AM, Mike Frysinger wrote: >> Because many traditional implementations of mktemp/mkstemp suck. > > and many modern implementations work perfectly fine. why is the default > to penalize good/fixed versions ? how about we flip this in config-top.h > like the attached patch ? Yes,

Re: avoid mktemp/mkstemp internally

2016-05-16 Thread Mike Frysinger
On 16 May 2016 10:02, Chet Ramey wrote: > On 5/13/16 2:40 PM, Mike Frysinger wrote: > > i was pointed at a bug report for FreeBSD systems [1] where running lots > > of processes in parallel would randomly fail with errors like: > > cannot make pipe for process substitution: File exists > > > > u

Re: avoid mktemp/mkstemp internally

2016-05-16 Thread Chet Ramey
On 5/13/16 2:40 PM, Mike Frysinger wrote: > i was pointed at a bug report for FreeBSD systems [1] where running lots > of processes in parallel would randomly fail with errors like: > cannot make pipe for process substitution: File exists > > upstream FreeBSD addressed this by defining USE_MKTEM

avoid mktemp/mkstemp internally

2016-05-13 Thread Mike Frysinger
i was pointed at a bug report for FreeBSD systems [1] where running lots of processes in parallel would randomly fail with errors like: cannot make pipe for process substitution: File exists upstream FreeBSD addressed this by defining USE_MKTEMP [2] & USE_MKSTEMP [3] when building bash. looking