From owner-freebsd-current Mon Jan 11 00:39:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00729 for freebsd-current-outgoing; Mon, 11 Jan 1999 00:39:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00724 for ; Mon, 11 Jan 1999 00:39:48 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id AAA90904; Mon, 11 Jan 1999 00:39:14 -0800 (PST) (envelope-from dillon) Date: Mon, 11 Jan 1999 00:39:14 -0800 (PST) From: Matthew Dillon Message-Id: <199901110839.AAA90904@apollo.backplane.com> To: "Carlos C. Tapang" Cc: "Jos Backus" , Subject: Re: Two seem-to-be bugs with 3.0-SNAP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Ah, I missed that one. pwd_mkdb was earlier modified to do locking :> (which it didn't do before). So now that it does, programs that :> use it shoulds either use pwd_mkdb's -N option so they can hold their :> own lock all the way through, or not hold a lock. : :Won't this require a change in sysinstall also? : :Carlos C. Tapang :http://www.genericwindows.com I don't think so. sysinstall does not appear to lock the password file on its own. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message