From owner-freebsd-hackers Thu May 2 15:39:13 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 21E4237B405 for ; Thu, 2 May 2002 15:39:05 -0700 (PDT) Received: from localhost (jjirsa@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) with ESMTP id g42MclP20483; Thu, 2 May 2002 15:38:47 -0700 Date: Thu, 2 May 2002 15:38:47 -0700 (PDT) From: Jeff Jirsa To: "Matthew D. Fuller" Cc: Subject: Re: bug in pw, freebsd 4.5 In-Reply-To: <20020502173110.B22449@over-yonder.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 May 2002, Matthew D. Fuller wrote: > > What do people think of using the external lock file (well, I can't > actually think of any OTHER way to do it, so...)? I'm thinking /var/run, > but on the flipside just putting it in /etc might be cleaner. Comments? > 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. - Jeff ============== Jeff Jirsa jjirsa@hmc.edu ============== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message