From owner-freebsd-questions Wed Apr 9 20:21:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA09069 for questions-outgoing; Wed, 9 Apr 1997 20:21:45 -0700 (PDT) Received: from mail.futuresouth.com (mail.futuresouth.com [207.141.254.21]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA09064 for ; Wed, 9 Apr 1997 20:21:37 -0700 (PDT) Received: from shell.futuresouth.com (shell.futuresouth.com [207.141.254.20]) by mail.futuresouth.com (8.8.5/8.8.5) with ESMTP id WAA16924; Wed, 9 Apr 1997 22:21:35 -0500 (CDT) From: Tim Tsai Received: (from tim@localhost) by shell.futuresouth.com (8.8.5/8.8.5) id WAA06433; Wed, 9 Apr 1997 22:21:35 -0500 (CDT) Message-Id: <199704100321.WAA06433@shell.futuresouth.com> Subject: Re: multi-user adduser In-Reply-To: from Doug White at "Apr 9, 97 08:12:00 pm" To: dwhite@resnet.uoregon.edu Date: Wed, 9 Apr 1997 22:21:35 -0500 (CDT) Cc: tim@futuresouth.com, questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Does anybody have an adduser script that's multi-user compatible? We > > need a script where our staff members can run it simultaneously without > > worrying about UID conflicts, etc. > Editing the password file simultaneously is asking for trouble. I don't > think it is possible, as one person will spam the changes another makes. Actually we just need to add users. Only one person (me) would edit the password file. I looked at the code some last night and it doesn't seem too bad. All we really need is to make sure the UID/GID is unique which can be done via an external lock file. The rest of the program already handles locking, etc. correctly. Is there anything else I am missing? > You have too many people adduser'ing ;) Well, it's convenient to be able to add new users while we're on the phone with them and check for problems. We add users at multiple locations so having one person to do it all isn't very practical. Our billing software has an Unix interface that would call adduser as a daemon, actually. Perhaps it's time for us to install that. Thanks, Tim