From owner-freebsd-current Sat Dec 12 18:03:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26553 for freebsd-current-outgoing; Sat, 12 Dec 1998 18:03:05 -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 SAA26546 for ; Sat, 12 Dec 1998 18:03:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id SAA14359; Sat, 12 Dec 1998 18:03:02 -0800 (PST) (envelope-from dillon) Date: Sat, 12 Dec 1998 18:03:02 -0800 (PST) From: Matthew Dillon Message-Id: <199812130203.SAA14359@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: minor vipw/pwd_mkdb changes commited Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've made a few minor fixes to vipw and pwd_mkdb to handle a master.passwd race condition (note: there are no security issues with the race). Also, pwd_mkdb has been slightly modified to lock the source file. This file is typically a temporary file when pwd_mkdb is run from vipw (etc...). However, when pwd_mkdb is run manually (say, from a script), a race between pwd_mkdb and someone editing master.passwd, running passwd, chpass, etc... can ensue whereby the latter programs replace master.passwd and regenerate the .db files while the original pwd_mkdb is still running, causing the db files to reflect an out-of-date master.passwd. Again, minor bugs but worth fixing. -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