Date: Thu, 29 May 1997 09:12:03 -0700 (MST) From: Don Yuniskis <dgy@rtd.com> To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-hackers@freefall.FreeBSD.org Subject: Re: uucp uid's Message-ID: <199705291612.JAA06181@seagull.rtd.com> In-Reply-To: <19970529083654.WR06258@uriah.heep.sax.de> from "J Wunsch" at May 29, 97 08:36:54 am
next in thread | previous in thread | raw e-mail | index | archive | help
It seems that J Wunsch said: > As Don Yuniskis wrote: > > > A bit of confusion on my part, perhaps... > > There's too much confusion about UUCP UIDs on any Unix i've seen so > far. :) Yes :-( If only that was the ONLY confusing issue... :> > > Shouldn't the uucp uid be that of the uucp *administrator*? > > I've seen both. It's a pain in the butt on every system that you > first gotta look who's who. > > > (i.e. the owner of the uucp files, processes, etc.). And, > > All the UIDs should be identical however, i.e. the UUCP administrator > has the same UID and group as all the UUCP dialin accounts. I've > never seen a system that doesn't handle it this way. I have a couple of (older) SysV derivatives that had uucp own the files and nuucp be the working "public" login. Thereafter, additional logins were either created with the same uid as nuucp (but appearing later in /etc/passwd) or separate accounts of the form "u<host>" (easier to track who's doing what...). Having the administrative id the same as the working id I guess is just annoying since it doesn't allow you to 'su - uucp' before modifying any of the configuration files of creating new directories. Annoying when you create a directory and it ends up as root.wheel until uucp actually tries to USE that directory later... :-( I guess the short term solution (for me) is to just change the home and shell fields for the uucp login to be more consistent with those of an account administrator instead of a uucp service... And create the extra logins for the working uid's. Thanks! --don
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705291612.JAA06181>