Path: utzoo!attcan!telly!eci386!clewis
From: clewis@eci386.uucp (Chris Lewis)
Newsgroups: comp.unix.xenix
Subject: Re: SCO dial-in site install help
Message-ID: <1989Jul28.193716.21779@eci386.uucp>
Date: 28 Jul 89 19:37:16 GMT
References: <20741@cup.portal.com> <266@mlfarm.UUCP>
Reply-To: clewis@eci386.UUCP (Chris Lewis)
Organization: R. H. Lathwell Associates: Elegant Communications, Inc.
Lines: 34

Not to pick on anyone specific, but:

In article <266@mlfarm.UUCP> ron@mlfarm.UUCP (Ronald Florence) writes:
>Mark, it sounds like you are running uucico as the login shell for
>your dial-in line.

I've seen about 5 responses that uucico is the "login shell for your
dial-in line".  Which is incorrect by implication, implying that once 
set up that way, you can't use your dial-in line for anything but uucico.

/etc/passwd allows you to set the "login shell" for a specific *user*, 
*not* line.  The originator of this thread set up a *uucico* login, and
logged in using that userid, so uucico started up.  Which would have
happened no matter where he logged in from (console, serial port, streams
channel, dial in, socket, and even "su" in some cases).  The only thing that 
mattered was that he used a userid that he had assigned to be a uucico login.

Uucico logins are intended to be the userid that another *machine* uses
when it calls your *machine*.

All he needs to remember is "use the same login name you normally do".
Don't matter where you come from...

Mind you, since he didn't seem to understand this, I hesitate to imagine
that a uucico login is of any use to him whatsoever...  Though, sometimes
the documentation leaves a little to be desired as to the real distinction
between "dial-in access for a machine" and "dial-in access for a user".

Read the manual page for /etc/passwd...
-- 
Chris Lewis, R.H. Lathwell & Associates: Elegant Communications Inc.
UUCP: {uunet!mnetor, utcsri!utzoo}!lsuc!eci386!clewis
Phone: (416)-595-5425