Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-spam!mordor!lll-tis!ptsfa!ihnp4!inuxc!iuvax!ndmath!ndcheg!evan
From: evan@ndcheg.UUCP (Evan Bauman)
Newsgroups: comp.unix.questions
Subject: Re: More Problems with Sys V uucp
Message-ID: <109@ndcheg.UUCP>
Date: Thu, 18-Jun-87 11:54:24 EDT
Article-I.D.: ndcheg.109
Posted: Thu Jun 18 11:54:24 1987
Date-Received: Mon, 22-Jun-87 00:48:48 EDT
References: <3950@jade.BERKELEY.EDU>
Organization: University of Notre Dame
Lines: 30
Summary: Check the target system for lock files


In article <3950@jade.BERKELEY.EDU>, richmon@violet.berkeley.edu (Michael Richmond) writes:
> Thanks to everyone who helped me with my earlier uucp problems -
> I managed to get through to the system I was calling at last.
> Now, however, as soon as the connection is made, something goes
> wrong, as shown by the following uucico output:
> 
> (...machine dials, phone rings, other computer answers and whines....)
> 	login called
> 	wanted "" got that
> 	ASSERT ERROR (uucico)  pid: 1386  (6/13-14:33:58)  BAD WRITE2  (0)
> 
> So, my guess is that there is a problem when my system tries to start 
> writing something (a log file? the file I'm trying to receive?) and doesn't
> have permission? Well, probably not, since I've run the job as root and the
> same error message still appears. Can anyone help me out with this? Thank
> you very much, in advance.

This sounds like the system you are calling has either a lock file
or a system status file in its uucp spool directory.  Before you
start the call, make sure these files do not exist on the target
machine.  The files will probably have the name
/usr/spool/uucp/LCK..SYSNAME
or
/usr/spool/uucp/STST.SYSNAME

where SYSNAME is the name of your computer.

  Evan Bauman
  ..!seismo!iuvax!ndmath!ndcheg!evan