From owner-freebsd-questions Wed May 5 13:53:27 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mercury.jorsm.com (mercury.jorsm.com [207.112.128.9]) by hub.freebsd.org (Postfix) with ESMTP id 70EC215551 for ; Wed, 5 May 1999 13:53:24 -0700 (PDT) (envelope-from jer@jorsm.com) Received: from localhost (jer@localhost) by mercury.jorsm.com (8.8.7/8.8.7) with SMTP id PAA10058 for ; Wed, 5 May 1999 15:53:24 -0500 (CDT) Date: Wed, 5 May 1999 15:53:24 -0500 (CDT) From: Jeremy Shaffner To: questions@freebsd.org Subject: pw(8) and locking Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While looking for information on pw(8) and whether or not it provides file locking for the various password files, I came across this: http://www.freebsd.org/cgi/getmsg.cgi?fetch=379125+382335+/usr/local/www/ db/text/1999/freebsd-questions/19990110.freebsd-questions /usr/src/usr.sbin/pw/pw.c in 3.1-RELEASE does indeed reflect this change. (It's there in 2.2.8) Why was this removed in 3.X? Does 'pw' provide *any* locking at all? Also, is there any performance improvement in using pw to add users instead of a custom script that appends to /etc/master.passwd and calls pwd_mkdb manually? Is this essentially what pw does, or does it manipulate the database directly? Thanks. -Jeremy -=========================================================================- Jeremy Shaffner JORSM Internet, Regional Internet Services Senior Technical Support 7 Area Codes in Chicagoland and NW Indiana jer@jorsm.com 100Mbps+ Connectivity, 56K-DS3, V.90, ISDN support@jorsm.com Quality Service, Affordable Prices http://www.jorsm.com Serving Gov, Biz, Indivds Since 1995 -=========================================================================- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message