john@jwt.UUCP (John Temples) (04/27/91)
Here's an excerpt of the output of uustat -m on my system: bilver 2C 04/26-23:30 Locked TALKING tarpit 1C 04/27-01:17 CAN'T ACCESS DEVICE uunet 1C 04/27-01:17 WRONG TIME TO CALL vicstoy 2C 04/27-01:17 CAN'T ACCESS DEVICE Why am I getting WRONG TIME TO CALL for uunet, when I should be getting CAN'T ACCESS DEVICE like the others? uunet is a time-restricted call, while the others aren't, but a call to uunet is valid at 01:17. A failed connect to uunet always gives WRONG TIME TO CALL, regardless of the cause. Is this a bug? -- John W. Temples -- john@jwt.UUCP (uunet!jwt!john)
hackney@moxie.hou.tx.us (Greg Hackney) (04/27/91)
john@jwt.UUCP (John Temples) writes: > Here's an excerpt of the output of uustat -m on my system: > uunet 1C 04/27-01:17 WRONG TIME TO CALL > call to uunet is valid at 01:17. A > failed connect to uunet always gives WRONG TIME TO CALL, regardless of > the cause. Is this a bug? Sounds like you might have *two* entries for uunet in the /usr/lib/uucp/Systems file. I've seen what you describe happen when it tries the first valid entry, and gives the message on the second. -- Greg Hackney hack@moxie.hou.tx.us
bill@twg.bc.ca (Bill Irwin) (05/01/91)
john@jwt.UUCP (John Temples) writes:
: A
: failed connect to uunet always gives WRONG TIME TO CALL, regardless of
: the cause. Is this a bug?
I suspect your entry for uunet in the Systems file has a time
specification that is being misinterpreted. Show us what the
entry looks like.
: --
: John W. Temples -- john@jwt.UUCP (uunet!jwt!john)
--
Bill Irwin - The Westrheim Group - Vancouver, BC, Canada
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
uunet!van-bc!twg!bill (604) 431-9600 (voice) | Your Computer
bill@twg.bc.ca (604) 430-4329 (fax) | Systems Partner