[29] in Zephyr_Bugs
[klee@ATHENA.MIT.EDU: vax 7.0D: zwgc]
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Wed May 23 00:14:20 1990
Date: Wed, 23 May 90 00:14:04 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: bug-zephyr@ATHENA.MIT.EDU
Apparently, a zwgc hung in this state *will* eventually give up, but
only after it has tried to subscribe to all of the subscriptions in
the .zephyr.subs file, 7 at a time.
I think this is broken. If a subscription attempt fails because
zwgc cannot contact the host manager, I would argue that it should
immediately give up. At the very least, it should keep track of how
many errors it's received, and give up after some small number in a
row (2 or 3, perhaps).
----- Forwarded message
From: klee@ATHENA.MIT.EDU
To: bugs@ATHENA.MIT.EDU
Subject: vax 7.0D: zwgc
Date: Tue, 22 May 90 12:36:52 EDT
System name: elric
Type and version: CVAXSTAR 7.0D (2 update(s) to same version)
Display type: SM
What were you trying to do?
Log in from dialup.
What's wrong:
As part of the default login process, my login scripts
tried to start a zwgc. Since I didn't have a hostmanager
running at the time, the zwgc process printed the message
"connection timed out while setting location".
It then failed to exit, and sat there, ignoring all keyboard
interrupts.
What should have happened:
It should not have caused my entire login to hang.
Please describe any relevant documentation references:
man 1 zwgc
----- End of forwarded message
