On Sun, Oct 28, 2001 at 07:40:34PM -0800, Terry Lambert wrote: > By using the rename/create/signal approach, syslogd is > guaranteed to log new messages to the old file, despite the > rename, until signalled to close and reopen the file (or a > new file of another name, if syslog.conf is changed). > > If it created the file itself, there would be a potential > race issue that would remain unresolved, which is hidden by > the seperation of the create and the subsequent signal.
Come again? 1. syslogd calls open(2) with O_CREAT. At this point syslogd happily keeps the file open and writes to it. 2. I rename the file. As we all know, syslogd keeps writing to its open file. 3. syslogd is HUP'ed, goto #1. No muss, no fuss. So where is the race? Mike had the only justification so far -- that of permissions of the file. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
