Xref: utzoo comp.unix.sysv386:727 comp.unix.admin:218
Path: utzoo!attcan!uunet!utoday!sean
From: sean@utoday.UUCP (Sean Fulton)
Newsgroups: comp.unix.sysv386,comp.unix.admin
Subject: Re: UUCP (HDB) - urgent !
Message-ID: <1812@utoday.UUCP>
Date: 25 Sep 90 18:03:15 GMT
References: <1135@stasys.sta.sub.org> <1990Sep24.134639.360@wsrcc>
Reply-To: sean@utoday.UUCP (Sean Fulton)
Organization: UNIX Today!, Manhasset, NY
Lines: 23

In article <1990Sep24.134639.360@wsrcc> wolfgang@wsrcc (Wolfgang S. Rupprecht) writes:
>fkk@stasys.sta.sub.org (Frank Kaefer) writes:
>>I have a really severe problem with UUCP (HDB). I think this could be a
>>real bug of HDB UUCP and I urgently seek some advice. [...]
>>Here is some uucico -x9 output:
>uucico:  ^M^M^M^JStasys Starnberg^M^M^Jlogin: uufips^M^M^JPassword:got it
>uucico: sendthem (xxxxxx^M)
>>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.

-- 
Sean Fulton					sean@utoday.com
UNIX Today!					(516) 562-5430
 /* The opinions expressed above are not those of my employer */