Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 / QGSI 2.0; site qubix.UUCP
Path: utzoo!linus!decvax!decwrl!sun!idi!qubix!msc
From: msc@qubix.UUCP (Mark Callow)
Newsgroups: net.unix-wizards
Subject: can't restart rlogin daemon after single user
Message-ID: <1525@qubix.UUCP>
Date: Thu, 8-Nov-84 20:46:03 EST
Article-I.D.: qubix.1525
Posted: Thu Nov  8 20:46:03 1984
Date-Received: Sat, 10-Nov-84 03:46:53 EST
Distribution: net
Organization: Qubix Graphic Systems, San Jose, CA
Lines: 29

Every week we take our 11/750 running 4.2BSD down to single-user for
backups.  Almost every week the rlogin daemon refuses to run upon
return to multi-user operations.  After recompiling with -DDEBUG
to persuade it to print some error messages, rlogind says

	"bind: address already in use"

Obviously the previous rlogind didn't die cleanly when the system went
to single-user.

[Minor Flame]
Why does rlogind swallow all error messages.  I'd certainly like to get
messages when it has problems.  It doesn't even print anything on the
console or via syslog.  Is this a "feature" or a bug??
[Extinguish]

Does anyone know why rlogind didn't die cleanly?  The backups are done
early in the morning and as afar as I know there are no active rlogin
connections at the time we go to single-user.  However there are
undoubtedly some in state FIN_WAIT_2 due to the infamous bug.

We have no problems with any of the other network daemons.

What I can do about it? I'd like to get rid of the problem, but I'd settle
for a means of getting rlogind back to life without rebooting the system.
-- 
From the TARDIS of Mark Callow
msc@qubix.UUCP,  qubix!msc@decwrl.ARPA
...{decvax,ucbvax}!decwrl!qubix!msc, ...{amd,ihnp4,ittvax}!qubix!msc