Date: Sat, 4 May 2002 23:43:17 -0500 From: "Matthew D. Fuller" <fullermd@over-yonder.net> To: Jeff Jirsa <jjirsa@odin.ac.hmc.edu> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bug in pw, freebsd 4.5 Message-ID: <20020504234317.A21048@over-yonder.net> In-Reply-To: <Pine.LNX.4.33.0205021536030.18912-100000@odin.ac.hmc.edu>; from jjirsa@odin.ac.hmc.edu on Thu, May 02, 2002 at 03:38:47PM -0700 References: <20020502173110.B22449@over-yonder.net> <Pine.LNX.4.33.0205021536030.18912-100000@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com 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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020504234317.A21048>