[1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

The following issue has been set as RELATED TO issue 0001364. == https://austingroupbugs.net/view.php?id=1016 == Reported By:izabera

[1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1016 == Reported By:izabera Assigned

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

By process private I mean a method similar to how pax avoids name collisions when unpacking global extended headers as separate files, using the process id as part of the name of a subdirectory under $TMPDIR to hold those extractions as the default template. This convention isn't completely

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

Op 29-03-17 om 18:30 schreef shwares...@aol.com: > I agree something along these lines should be added. As worded now the > assumption looks to be more the system is a single user one, or > sandboxed to that effect, not a multi-user server. Yes. > It doesn't even have to be a different user; a

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

I agree something along these lines should be added. As worded now the assumption looks to be more the system is a single user one, or sandboxed to that effect, not a multi-user server. It doesn't even have to be a different user; a separate process that happens to use the same tmpnam()

[1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

The following issue has been UPDATED. == http://austingroupbugs.net/view.php?id=1016 == Reported By:izabera Assigned To:

[1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

The following issue has been UPDATED. == http://austingroupbugs.net/view.php?id=1016 == Reported By:izabera Assigned To:

[1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

The following issue NEEDS AN INTERPRETATION. == http://austingroupbugs.net/view.php?id=1016 == Reported By:izabera Assigned To:

[1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1016 == Reported By:izabera Assigned To:

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

< said: > Also, on Mac OS X and FreeBSD, 'link' turns out to act like 'ln': if a > directory or a symlink to it exists, the file is created inside it. This > is contrary to what the man page says, by the way. But in any case it > means I can't use it. Actually, no: When the utility is

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

No, there is no app dir structure mandated by POSIX. That is considered an administrative issue outside of the base POSIX scope, and is generally covered by packaging conventions like DEB and RPM as de facto standards. I don't think any platform implemented the proposed 1003.1j standard. Only

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

Stephane Chazelas wrote, on 07 Nov 2016: > > 2016-11-07 16:57:34 +, Stephane Chazelas: > [...] > > OK, sorry, I had assumed rename() would fail if the target exits > > already. > [...] > > BTW, in the spec of link(2): > > [EEXIST] > The

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

Stephane Chazelas wrote, on 07 Nov 2016: > > 2016-11-07 16:20:08 +, Geoff Clare: > [...] > > > How so? "mv -i" with /dev/null as stdin ("no" answer to prompt) > > > is not supposed to remove anything. > > > > Only if it prompts. If the existence check fails, mv

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

2016-11-07 16:57:34 +, Stephane Chazelas: [...] > OK, sorry, I had assumed rename() would fail if the target exits > already. [...] BTW, in the spec of link(2): [EEXIST] The path2 argument resolves to an existing directory entry or refers to a

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

2016-11-07 16:20:08 +, Geoff Clare: [...] > > How so? "mv -i" with /dev/null as stdin ("no" answer to prompt) > > is not supposed to remove anything. > > Only if it prompts. If the existence check fails, mv will not > prompt and will just call rename(). OK, sorry, I had assumed rename()

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

Stephane Chazelas wrote, on 07 Nov 2016: > > BTW, there's an issue in the spec for "mv": > > > EXIT STATUS > > > > The following exit values shall be returned: > > > >  0 > > All input files were moved successfully. > > >0 > > An error occurred.

RE: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

> -Original Message- > From: Geoff Clare [mailto:g...@opengroup.org] > Sent: Monday, November 07, 2016 5:20 PM > To: austin-group-l@opengroup.org > Subject: Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set > -C > > That seems to be in contradiction

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

Stephane Chazelas wrote, on 07 Nov 2016: > > 2016-11-07 15:40:15 +, Geoff Clare: > [...] > > > Same problem with "mv" (which I think would work just > > > as well (with LC_ALL=C mv -i < /dev/null 2> /dev/null)) > > > > No, mv -i doesn't work just as well - it has

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

2016-11-07 16:10:01 +, Stephane Chazelas: [...] >mv -i a b < /dev/null 2>&- > > seem to work with GNU or Solaris10 mv (in that it returns with > an error when a prompt fails to be issued) but not with > FreeBSD's [...] Sorry, I messed up my tests on Solaris. Solaris /bin/mv doesn't issue

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

2016-11-07 15:57:25 +, Stephane Chazelas: > 2016-11-07 15:40:15 +, Geoff Clare: > [...] > > > Same problem with "mv" (which I think would work just > > > as well (with LC_ALL=C mv -i < /dev/null 2> /dev/null)) > > > > No, mv -i doesn't work just as well - it has a race condition. > > If a

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

2016-11-02 13:32:44 +, Martijn Dekker: [...] > If both 'mkdir' and 'ln' operate atomically, there could be a safe > workaround for creating a regular file directly under /tmp. It would > involve creating a (very) temporary directory under /tmp using 'mkdir > -m700', then creating the file

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

Op 07-11-16 om 03:55 schreef Shware Systems: > To last question, yes, but the effects are supposed to be documented so > generic guard code that may invoke platform specific pre-ln attempt > handling can be written. This is a compromise to disqualifying a system > that defines additional file

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

To last question, yes, but the effects are supposed to be documented so generic guard code that may invoke platform specific pre-ln attempt handling can be written. This is a compromise to disqualifying a system that defines additional file types from being considered conforming at all. In a

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

Op 02-11-16 om 10:51 schreef Stephane Chazelas: > At the moment, there's no way (that I know) to create a temp file > reliably with POSIX utilities (though it may be possible to create a > temp dir reliably, which is generally a better idea than creating a temp > file in a world writable directory

Certified shells (was: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C)

Joerg Schilling wrote, on 02 Nov 2016: > > Stephane Chazelas wrote: > > > Has ksh93 ever been certified as a POSIX conformant shell? > > Actually, have any other shell than ksh88 and bash been > > certified? As far as I'm aware

RE: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

> -Original Message- > From: Geoff Clare [mailto:g...@opengroup.org] > Sent: Tuesday, November 01, 2016 11:27 AM > To: austin-group-l@opengroup.org > Subject: Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set > -C > > > Why are we bothering to

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

Stephane Chazelas wrote: > 2016-11-02 10:13:37 +, Geoff Clare: > [...] > > We believe that all modern shells are already using O_EXEC. The one > > notable shell that doesn't is ksh88 but I don't count that as modern, > > since ksh93 is its modern replacement. >

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

Robert Elz wrote, on 01 Nov 2016: > > Without getting into the specifics of the proposed change yet, I'd > like someone to explain just what is the fascination with using -C > and '>' for making lock files? > > The time honoured way of making lock files (since way, way, back)

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

Without getting into the specifics of the proposed change yet, I'd like someone to explain just what is the fascination with using -C and '>' for making lock files? The time honoured way of making lock files (since way, way, back) is via the use of link(2) (or ln(1)) which has always provided for

Re: [1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

On Thu, Oct 20, 2016 at 04:40:36PM +, Austin Group Bug Tracker wrote: > > A NOTE has been added to this issue. > == > http://austingroupbugs.net/view.php?id=1016 >

[1003.1(2013)/Issue7+TC1 0001016]: race condition with set -C

A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1016 == Reported By:izabera Assigned To: