Xref: utzoo comp.sys.att:10703 comp.unix.sysv386:1650
Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!umich!sharkey!cfctech!teemc!ka3ovk!raysnec!shwake
From: shwake@raysnec.UUCP (Ray Shwake)
Newsgroups: comp.sys.att,comp.unix.sysv386
Subject: uucp vs. nuucp logins <was: No Passwd for nuucp>
Message-ID: <120@raysnec.UUCP>
Date: 28 Oct 90 16:37:39 GMT
References: <1990Oct22.211639.14436@mccc.uucp> <1990Oct27.203150.13610@jpradley.uucp>
Followup-To: comp.sys.att
Organization: IRS/CI - Technical Solutions Branch
Lines: 17

jpr@jpradley.uucp (Jean-Pierre Radley) writes:

>BTW, what's the point of 'nuucp' as a public, unpassworded access instead of
>just plain 'uucp'?

	While many systems are delivered with a "uucp" login running the
uucico daemon shell, the vendors (and users) who follow this practice
overlook the value of having a uucp *administrative* account to handle
system configuration and maintenance. That account requires an interactive
shell.

	Our practice - and that of some vendors - is to support a default
uucp login with an interactive shell (like /bin/sh), plus a default nuucp
account with a uucico daemon shell. As required, I can then proceed to add
additional uucico shell accounts.

						shwake@rsxtech