Taylor uucp 1.06.1 auf Windows NT 4

ian@cygnus.com ian@cygnus.com
Fri Jan 2 09:02:00 GMT 1998

In gnu-win32 mh@mike.franken.de (Michael Hirmke) writes:

>uucico <xxx> - (1998-01-02 14:07:25.33 1062) DEBUG: floop: No work for master
>uucico <xxx> - (1998-01-02 14:07:25.34 1062) DEBUG: ftsendcmd: Sending command "H"
>uucico <xxx> - (1998-01-02 14:07:25.34 1062) DEBUG: fconn_io: Writing 512 "H\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\
>uucico <xxx> - (1998-01-02 14:09:26.81 1062) DEBUG: fconn_io: Wrote 512 of 512, read 9 of 16327
>uucico <xxx> - (1998-01-02 14:09:26.81 1062) DEBUG: fconn_io: Read 9 "\020OOOOOOO\000"
>uucico <xxx> - (1998-01-02 14:09:26.81 1062) DEBUG: floop: Waiting for data
>uucico <xxx> - (1998-01-02 14:09:37.25 1062) ERROR: Line disconnected

This isn't a valid sequence of commands.  If possible, you should see
what the uucico on the other end reports.

After your uucico sends the H command, it should see an HY or HN
response.  Instead, it waits 2 minutes and then gets an over-and-out
response, which implies that the remote uucico timed out waiting for a
command.  Try to find out whether the remote uucico saw anything at
all.  This looks like it might be a problem somewhere in the cygwin32
networking support.  I'm just guessing, though.

For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

More information about the Cygwin mailing list