Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cuae2!ihnp4!houxm!hropus!jrw
From: jrw@hropus.UUCP (Jim Webb)
Newsgroups: net.unix-wizards
Subject: Re: 4.3bsd uucico log entry question
Message-ID: <765@hropus.UUCP>
Date: Thu, 6-Nov-86 17:34:18 EST
Article-I.D.: hropus.765
Posted: Thu Nov  6 17:34:18 1986
Date-Received: Fri, 7-Nov-86 23:21:50 EST
References: <2410004@nucsrl.UUCP>
Organization: Bell Labs, Holmdel, NJ
Lines: 20

> Our uucp log for the system chinet (from whom we get news) shows
> the following entry:
> 
> UUCP chinet (11/5-17:50-5930) SUCCEEDED (call to chinet )
> UUCP chinet (11/5-17:52-5930) FAILED (imsg 1)
> **NSC** chinet (11/5-18:08-5944) FAILED (LOGIN)
> **NSC** chinet (11/5-18:08-5944) FAILED (call to chinet )

>                          I tried looking for NSC in the sources for
> uucp but couldn't find it (via egrep NSC /usr/src/usr.bin/uucp/*.[ch]

**NSC** is the login of the process (5944) that failed in calling chinet,
so it is no wonder it did not show up in an egrep ;-).  The imsg() routine
is used before any protocol (read g) is used, so I would imagine that
either your uucico is messed up, or, more likely, you are having line
noise/flow control problems that are messing up its reading of the protocol
message.
-- 
Jim Webb             "Out of phase--get help"          ...!ihnp4!hropus!jrw
		"Use the Force, Read the Source"