From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] v7 uucp debugging help requested
Date: Fri, 3 Jul 2020 16:38:31 -0600 [thread overview]
Message-ID: <01f8f896-9921-6c55-8dc2-6b9859f2f230@tnetconsulting.net> (raw)
In-Reply-To: <CAP2nic3UNxqi-obHwB5H+Ee+x5MKsd=eBrwhVbX+Ao3AgVPx=g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2309 bytes --]
On 7/3/20 2:52 PM, Adam Thornton wrote:
> I've built UUCP, set a node name, and set it up on the pi.
>
> I can execute uucico to send files, and it, frustratingly, almost works.
Which system are you referring to here? The Pi or V7?
> From the Pi side, I see (with uulog):
>
> uucico v7 - (2020-07-03 08:11:34.97 23106) Calling system v7 (port TCP)
> uucico v7 - (2020-07-03 08:11:42.25 23106) Login successful
> uucico v7 - (2020-07-03 08:11:44.44 23106) Handshake successful
> (protocol 'g' sending packet/window 64/3 receiving 64/7)
> uucico v7 adam (2020-07-03 08:11:51.61 23106) Sending
> /home/adam/git/simh/sim_scsi.h (6780 bytes)
> uucico v7 adam (2020-07-03 08:16:21.79 23106) ERROR: Timed out waiting
> for packet
> uucico v7 - (2020-07-03 08:16:21.80 23106) Protocol 'g' packets: sent
> 86, resent 6, received 1
I'm a little surprised that you're trying to use the 'g' protocol to
talk to v7. I thought the 'g' protocol came out later for TCP over
Ethernet connections. As such I wonder if UUCP on v7 supports the 'g'
protocol.
I think that Clem knows a LOT more about this than I do.
I'm ignorantly asking questions.
> uucico v7 - (2020-07-03 08:16:21.80 23106) Errors: header 2, checksum 0,
> order 0, remote rejects 0
> uucico v7 - (2020-07-03 08:16:22.51 23106) Call complete (283 seconds
> 5440 bytes 19 bps)
>
> So it's clearly logging in, and if I telnet in directly, the v7 end is
> starting uucico as expected:
>
> login: pi-uucp
> Password:
> Shere
Shouldn't that be something more like the following?
Shere=v7
What does 'uuname -l' (or '--local') show? (I'm much more familiar with
Taylor UUCP than I am the UUCP in v7.
> uulog -x on the v7 side has no output, and nothing ever appears in the
> spool directory, which I suspect is a direct result of the timeout
> waiting for packet.
>
> So my question is, what else do I do to debug this? Clearly the pi
> (Taylor UUCP) side is expecting something else--maybe an
> acknowledgement?--from the v7 side to let it know the transmission was
> successful.
>
> Any help would be appreciated.
I've not messed with this particular problem in probably 2 years and
I've forgotten more than comments above.
--
Grant. . . .
unix || die
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4013 bytes --]
next prev parent reply other threads:[~2020-07-03 22:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 20:52 Adam Thornton
2020-07-03 21:26 ` Clem Cole
2020-07-03 22:38 ` Grant Taylor via TUHS [this message]
2020-07-04 0:28 ` Clem Cole
2020-07-04 0:31 ` Clem Cole
2020-07-04 19:33 ` Adam Thornton
2020-07-04 20:02 ` Clem Cole
2020-07-04 21:58 ` Adam Thornton
2020-07-05 5:42 ` Adam Thornton
2020-07-03 22:50 ` John Cowan
2020-07-04 16:33 ` Adam Thornton
2020-07-04 18:34 ` John Cowan
2020-07-04 18:44 ` Jon Forrest
2020-07-04 19:34 ` Adam Thornton
2020-07-06 4:12 ` Dave Horsfall
2020-07-06 4:18 ` Warner Losh
2020-07-06 6:51 ` arnold
2020-07-06 7:11 ` Michael Usher via TUHS
2020-07-06 13:57 ` Clem Cole
2020-07-06 18:51 ` John Cowan
2020-07-06 19:19 ` arnold
2020-07-06 19:36 ` John Cowan
2020-07-06 19:58 ` John Cowan
2020-07-06 20:48 ` Clem Cole
2020-07-07 6:21 ` arnold
2020-07-10 5:05 ` Win Treese
2020-07-10 5:19 ` Warner Losh
2020-07-14 2:52 ` Dave Horsfall
2020-07-06 21:47 ` Dave Horsfall
2020-07-07 6:23 ` arnold
2020-07-07 21:45 ` Dave Horsfall
2020-07-06 21:18 ` Dave Horsfall
2020-07-06 21:47 ` John Cowan
2020-07-07 1:30 ` [TUHS] Editors (was: v7 uucp debugging help requested) Greg 'groggy' Lehey
2020-07-04 0:35 [TUHS] v7 uucp debugging help requested Norman Wilson
2020-07-07 19:20 Norman Wilson
2020-07-07 22:47 ` Rob Pike
2020-07-07 23:42 ` Adam Thornton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01f8f896-9921-6c55-8dc2-6b9859f2f230@tnetconsulting.net \
--to=tuhs@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).