[2009] in Release_7.7_team
Re: syncconf hack
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Sat Dec 4 19:28:16 1999
Message-Id: <199912050028.TAA59030@deliverator.mit.edu>
From: Jonathon Weiss <jweiss@MIT.EDU>
To: Greg Hudson <ghudson@MIT.EDU>
cc: source-reviewers@MIT.EDU, release-team@MIT.EDU
In-reply-to: Your message of "Sat, 04 Dec 1999 16:19:30 EST."
<199912042119.QAA20721@small-gods.mit.edu>
Date: Sat, 04 Dec 1999 19:28:04 -0500
The patch looks good. I don't think sleep will help, unles you can
get the unclean reboot to wait till the sleep is over. :-)
> hotline has asked for relief from this problem. As it is after drop
> date, I think we want to do something very conservative. I suggest
> applying this patch to syncconf and putting the new file out to field
> early next week without bumping the patch level. PUBLIC=true machines
> will take the new version of syncconf and hopefully stop seeing the
> problem for the most part; PUBLIC=false machines are not as prone to
> the problem because they don't re-sync the network configuration on
> every boot.
This seems like a nice conservative approach that is reasonable if
hotline considers relief from the problem to be important (as you've
suggested they do). However, I don't think that PUBLIC=true machiens
will update syncconf automatically unless you update teh statfile too,
or was that implied?
Jonathon
