uucico hang between sVr3.2 and sVr4

Thread View: comp.bugs.sys5

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Paul de Bra Thu, 03 Jan 1991 11:38

#270

Author: Paul de Bra
Date: Thu, 03 Jan 1991 11:38

17 lines
1100 bytes

I tried to connect 2 386 systems (at low baud rate to make sure)
using a standard hardwired line. This connection works fine with
cu, and with kermit.

When the sVr4 system calls the sVr3.2 system with uucico, everything
goes well.
When the sVr3.2 system calls the sVr4 system with uucico it hangs
right after getting the Shere=thename^@ from the sVr4 system (where
'thename' stands for the hostname on the sVr4 system).
The uucico on the sVr3.2 system times out and exits.
The uucico on the sVr4 system does not time out but just hangs
indefinetely.

Has anyone else had problems with uucp to sVr4 systems?

Paul.
(debra@research.att.com, debra@win.tue.nl)

Re: uucico hang between sVr3.2 and sVr4

#277

Author: Leslie Mikesell
Date: Thu, 03 Jan 1991 18:52

27 lines
1879 bytes

In article <1658@svin02.info.win.tue.nl> debra@svin02.info.win.tue.nl (Paul de Bra) writes:

>When the sVr4 system calls the sVr3.2 system with uucico, everything
>goes well.
>When the sVr3.2 system calls the sVr4 system with uucico it hangs
>right after getting the Shere=thename^@ from the sVr4 system (where
>'thename' stands for the hostname on the sVr4 system).
>The uucico on the sVr3.2 system times out and exits.
>The uucico on the sVr4 system does not time out but just hangs
>indefinetely.

One possibility that is not entirely obvious is a syntax error in
the Permissions file (perhaps a continuation line where the previous
line does not have a \).  The reason it could act differently when
calling vs. being called is that the Permissions entry is located
by the MACHINE= entry on outbound calls, but on inbound calls it
is the LOGNAME= entry (and the first match is used).  For instance
if your first entry on the SysVr3.2 machine has LOGNAME=nuucp
and that is what the other machine logs in as, it wouldn't read any
farther in Permissions.  Then if the MACHINE= entry for the SysVr4
system is the last entry in the file and the syntax error is there
or somewhere in between, you get the silent death syndrome.  The reverse
could apply to the SysVr4 machine if they haven't fixed uucico to
give a reasonable error message.

Les Mikesell
  les@chinet.chi.il.us

Re: uucico hang between sVr3.2 and sVr4

#272

Author: Gregory G. Woodbury
Date: Fri, 04 Jan 1991 01:05

22 lines
1575 bytes

In article <1658@svin02.info.win.tue.nl> debra@svin02.info.win.tue.nl (Paul de Bra) writes:
>When the sVr3.2 system calls the sVr4 system with uucico it hangs
>right after getting the Shere=thename^@ from the sVr4 system (where
>'thename' stands for the hostname on the sVr4 system).
>The uucico on the sVr3.2 system times out and exits.
>The uucico on the sVr4 system does not time out but just hangs
>indefinetely.
>
>Has anyone else had problems with uucp to sVr4 systems?

	Haven't talked to a sVr4 system yet, but it sounds very much
like the problem that occurs when my sVr3.2.0 system talks to the amiga
version of uucico.  All it took on my end was to add a final couplet to
the chat script that delayed once and then sent a DLE (control-P) down
the line.  This makes somebody somewhere wake up and carry on.

	Give it a try.
-- 
Gregory G. Woodbury @ The Wolves Den UNIX, Durham NC
UUCP: ...dukcds!wolves!ggw   ...mcnc!wolves!ggw           [use the maps!]
Domain: ggw@cds.duke.edu     ggw%wolves@mcnc.mcnc.org
[The line eater is a boojum snark! ]           <standard disclaimers apply>

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads