On Wed, Jul 28, 2004 at 10:57:58AM -0700, Steve Bonds wrote: > > HP-UX? > > Alas, no. The mkstemp man page suggests using tmpfile() instead, which > generally means that HP won't fix any problems. > > ----- mktemp(3C) > Remarks: > These functions are provided solely for backward compatibility and > importability of applications, and are not recommended for new > applications where portability is important. For portable > applications, use tmpfile() instead (see tmpfile(3S)). > -----
Maybe we should follow this advice. > > The tempnam()/tmpfile() combination seems particularly difficult to use > compared with mkstemp(). I especially liked this warning: > > ----- tmpnam(3S) > WARNINGS > Between the time a file name is created and the file is opened, it is > possible for some other process to create a file with the same name. > This can never happen if that other process is using these functions > or mktemp, and the file names are chosen such that duplication by > other means is unlikely. > ----- Can we use tmpfile without tmpname? -chris > > At least HP documents their race conditions, eh? :( > > -- Steve > -- > To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
