From owner-freebsd-questions Thu Apr 10 02:33:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA25867 for questions-outgoing; Thu, 10 Apr 1997 02:33:10 -0700 (PDT) Received: from nero.in-design.com (root@nero.in-design.com [204.157.146.146]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA25861 for ; Thu, 10 Apr 1997 02:33:04 -0700 (PDT) Received: (from archive@localhost) by nero.in-design.com (8.8.5/8.8.5) id FAA25461; Thu, 10 Apr 1997 05:33:02 -0400 (EDT) Date: Thu, 10 Apr 1997 05:33:02 -0400 (EDT) From: Intuitive Design Archive To: Tim Tsai cc: dwhite@resnet.uoregon.edu, tim@futuresouth.com, questions@FreeBSD.ORG Subject: Re: multi-user adduser In-Reply-To: <199704100321.WAA06433@shell.futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Apr 1997, Tim Tsai wrote: > > > 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. > How about a cron job. This was mentioned before in a adduser cgi thingy, but it seams that it is also perfect for this option. Have people add info to a file in /tmp, or what have you, and every 20 min or whatever adduser in batch mode adds all the users in that file, erases it and you start over. The interface can be that of your billing software aslong as you can have it write certain info that you need it to write out in the adduser batch mood structure... Does that help... Intuitive Design Archive http://www.in-design.com archive@in-design.com