Xref: utzoo comp.unix.sysv386:791 comp.unix.admin:244
Newsgroups: comp.unix.sysv386,comp.unix.admin
Path: utzoo!telly!eci386!woods
From: woods@eci386.uucp (Greg A. Woods)
Subject: Re: UUCP (HDB) - urgent !
Message-ID: <1990Sep27.220045.2752@eci386.uucp>
Reply-To: woods@eci386.UUCP (Greg A. Woods)
Organization: Elegant Communications Inc.
References: <1135@stasys.sta.sub.org> <1990Sep24.134639.360@wsrcc> <1812@utoday.UUCP>
Distribution: world 
Date: Thu, 27 Sep 90 22:00:45 GMT

In article <1812@utoday.UUCP> sean@utoday.UUCP (Sean Fulton) writes:
> In article <1990Sep24.134639.360@wsrcc> wolfgang@wsrcc (Wolfgang S. Rupprecht) writes:
> >fkk@stasys.sta.sub.org (Frank Kaefer) writes:
> >>Here is some uucico -x9 output:
> >>uucico: imsg >^M^JUNIX System V/386 Release 3.2^M^Jstasys^M^JCopyright (C) 1984, 1986, 1987, 1988 AT&T^M^JCopyright (C) 1987, 1988 MiLOGIN FAILED - failed
> >  ******************^^^^*********************		
> >>uucico: exit code 101
> 
> Check /etc/passwd to make sure stasys has a valid account, a valid
> directory, and a valid shell (/usr/lib/uucp/uucico). The login itself
> was actually completed, it was the waiting for Shere= that died.
>
> I say this because we had the exact same problem here a while back,
> and it was something really obvious but took hours to figure out. Try
> replacing uucico with /bin/sh and login.

In other words, *ALWAYS* run /etc/pwck after you edit the password
file.  It does a good job of validating this very essential database.
In fact, if there is any chance of another user running passwd (or
chsh, should you have it) you should be using some sort of protective
wrapper around the editor, such as vipw, which could easily run pwck
for you.

Also, you need not change uucico with sh.  Just type
'<CTRL-P>Shere=nobody<LF>' and the cico will quietly go away (unless
your machine knows another named "nobody" :-) ).
-- 
						Greg A. Woods

woods@{eci386,gate,robohack,ontmoh,tmsoft}.UUCP
+1-416-443-1734 [h]  +1-416-595-5425 [w]    VE3-TCP	Toronto, Ontario CANADA