[541] in testers
vax 6.4R: rkinit
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Thu Dec 21 11:46:48 1989
Date: Thu, 21 Dec 89 11:46:25 -0500
From: Jonathan I. Kamens <jik@PIT-MANAGER.MIT.EDU>
To: testers@ATHENA.MIT.EDU
When I rkinit to a machine that does not have rkinitd installed
locally and is not activated, inetd immediately signals that it cannot
exec rkinitd.
However, rkinit hangs around for 60 seconds waiting for something
from the rkinitd that just isn't going to come.
Shouldn't rkinit notice immediately that rkinitd didn't run? Other
inetd clients (rlogin, telnet, etc.) seem to be able to do this....
jik