From owner-freebsd-questions Thu May 2 10:45: 6 2002 Delivered-To: freebsd-questions@freebsd.org Received: from speicher.org (sirius.speicher.org [209.74.10.51]) by hub.freebsd.org (Postfix) with ESMTP id 0E6C237B404 for ; Thu, 2 May 2002 10:45:02 -0700 (PDT) Received: from localhost (geoff@localhost) by speicher.org (8.11.6/8.11.6) with ESMTP id g42HkoY42426 for ; Thu, 2 May 2002 13:46:50 -0400 (EDT) (envelope-from geoff@speicher.org) Date: Thu, 2 May 2002 13:46:50 -0400 (EDT) From: "Geoffrey C. Speicher" To: freebsd-questions@FreeBSD.ORG Subject: concurrent pw(8) corrupts master.passwd sometimes? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ``Sometimes'' being the operative word. I am not able to reliably reproduce it, but it sure does happen. I don't know for sure that it is the fault of pw, but that's what I'm trying to determine. Here's the scenario: a user visits a web site and fills out a form to create an account with the site. When they press submit, a record is inserted into a database table holding their account information. This triggers a call to 'pw adduser ...' on the local machine so they have a home directory to store files and a personal email account. Usually it works fine, but under some circumstances master.passwd is left short, sometimes in the middle of a record. Anyone have any ideas that might save me some time while I'm looking at the pw sources? I'm starting to wonder if I should run 'nohup pw adduser ...'. (Please CC me on reply.) Thanks, Geoff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message