On 9/11/18 4:46 PM, Robert Elz wrote:
> If it is unspecified, then a script cannot start an async pipeline,
> then want to run another while the first is executing, with a
> different pipefail setting (different to that for the first) as as soon as
> the pipefail option is changed while the async
Date:Sat, 15 Sep 2018 19:54:20 -0400
From:Chet Ramey
Message-ID: <6236131b-b65d-7d08-c48a-fbca06fc2...@case.edu>
| The chance of this happening in the future, when it has not happened
| so far, is vanishingly small.
I agree that it would be very rare, which is
Geoff Clare wrote:
> Perhaps an acceptable solution would be:
>
> Add -mount to find with behaviour matching nftw() FTW_MOUNT.
>
> Add FTW_XDEV to nftw() with behaviour matching find -xdev and pax -X.
>
> Make it clear that find -xdev acts on the mount points and -mount does not.
It may be of
Siteshwar Vashisht wrote:
> > Bash and ksh93 (at least the latest version I have from git).
> >
> > $ ./src/cmd/ksh93/ksh -c 'type -t printf'
> > builtin
>
> This flag was added with last beta release of ksh (ksh93v-) that came out from
> AT This is related entry from changelog[1] :
>
>
Siteshwar Vashisht wrote:
> > It seems that these people are not talking with David Korn.
>
> I tried to reach dgk several times in last couple of years, but never
> managed to get a response from him. It would be great if he becomes active in
> the discussions again, but it's unlikely to
- Original Message -
> From: "Joerg Schilling"
> To: svashi...@redhat.com
> Cc: k...@munnari.oz.au, "chet ramey" ,
> austin-group-l@opengroup.org
> Sent: Saturday, September 15, 2018 1:23:42 PM
> Subject: Re: Status of pipefail for standardization
>
> Siteshwar Vashisht wrote:
>
>
