On Thu, May 02, 2002 at 03:38:47PM -0700 I heard the voice of Jeff Jirsa, and lo! it spake thus: > > Feel free to correct me if I'm wrong, but /var/run seems like the more > logical answer. Read-only / filesystems would have a hard time creating > temp lock files in /etc. If nothing else, make it something that's > easily configurable to avoid problems with read only filesystems.
Well, read-only / filesystems would have a hard time creating /etc/master.passwd.new in the middle of pw's actions, too :) /var/run isn't a perfect choice, but it doesn't seem a bad one, and there's rather a bit of precedent for using it for state files, which I'd call a lock file (PID files, Apache stores some state, log/named sockets, etc). -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Unix Systems Administrator | [EMAIL PROTECTED] Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
