On Tue, 16 Jun 2009 15:59:42 -0400 James Carlson wrote:
> Glenn Fowler writes:
> The Solaris one does a modest check to see if the name is unused. But
> since it doesn't hold onto that newly-created object, anyone else
> could slip in a millisecond after mktemp(1) exit and create that same
> object with nary a complaint observed.
> I don't see now it's an architectural distinction.
solaris does two extra calls { creat(2) or whatever and unlink(2) }
either of those two calls could fail, causing mktemp(1) to fail
gnu does not do the { creat unlink } and so doesn't have the associated error
handling
so the solaris implementation can/may fail in ways that the gnu implementation
cannot
e.g., what if the filesystem is full?
I don't like the -u option in either incarnation
but the incarnations are distinct
