On Tue, 2004-02-10 at 10:20, Ketil Froyn wrote: > While we're discussing this, it should be noted that creating a directory > directly under /service may lead to trouble with logging. If you do this: > > mkdir /service/NAME > mkdir /service/NAME/log > > then svscan may have detected /service/NAME and seen that there is no > logging-directory in it before you complete the second mkdir (race > condition), and then logging will not work. If you want to put the > directory in /service, I recommend doing something like this: > > mkdir /tmp/NAME > mkdir /tmp/NAME/log > cp runfile /tmp/NAME > cp logrunfile /tmp/NAME/log > mv /tmp/NAME /service # atomic move, must not cross filesystems
or mkdir -p /service/NAME/log although putting the directory directly under /service is a bad idea imo *shrug* -Jeremy -- Jeremy Kitchen Systems Administrator [EMAIL PROTECTED] Kitchen @ #qmail on EFNet - Join the party! ..................... Inter7 Internet Technologies, Inc. www.inter7.com 866.528.3530 toll free 847.492.0470 int'l 847.492.0632 fax GNUPG key ID: 93BDD6CE
