Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sri-unix!MRC@SU-SCORE.ARPA From: MRC@SU-SCORE.ARPA Newsgroups: net.unix-wizards Subject: Re: rfnm's and 4.2bsd Message-ID: <12226@sri-arpa.UUCP> Date: Thu, 27-Sep-84 01:36:20 EDT Article-I.D.: sri-arpa.12226 Posted: Thu Sep 27 01:36:20 1984 Date-Received: Wed, 26-Sep-84 02:56:30 EDT Lines: 10 From: Mark CrispinIt is a horrible idea to test for bad leader. Interface reset should always be used as the condition to "reset everything". My old NCP code for WAITS ignored all messages from the IMP after IMP Ready cycled down until it got an Interface Reset. If it failed to get the Interface Reset within 10 (or was it 30?) seconds after IMP Ready/Host Ready were up, it dropped Host Ready, held it down a few seconds, then tried again. In general, this worked quite well. -------