Date: Tue, 17 Apr 2001 14:15:15 -0700 From: "Jason DiCioccio" <geniusj@bluenugget.net> To: "Darren Reed" <avalon@coombs.anu.edu.au>, "Alfred Perlstein" <bright@wintelcom.net> Cc: <freebsd-security@FreeBSD.ORG>, <net@FreeBSD.ORG> Subject: Re: non-random IP IDs Message-ID: <004201c0c783$7fe71df0$4904a8c0@epylon.lan> References: <200104172046.GAA04095@caligula.anu.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Darren Reed" <avalon@coombs.anu.edu.au> Subject: Re: non-random IP IDs > How long has your box been up ? How many changes to the system config > have been made since then ? If you're not there, and it reboots, will > it come up 100% functional ? Do your computers need some amount of > preventative maintenance like internal cleaning to deal with dust build > up, etc ? I don't know very many if any people that take their machines off the rack just to clean dust out of the case. > How many times do unscheduled reboots result in hardware not > spinning back up and at an inconevient time ? This would happen regardless of when/if you rebooted it. > Any non-trivial change to > startup (or bootup) sequence should be tested and how do you do that > without a reboot ? I use /usr/local/etc/rc.d, so for me it would be 'blah.sh stop && blah.sh start..' If you use rc.local or rc.* usually running the necessary commands while system is up is a good determination on whether it'll work, or putting it in a separate shell script and running that is even better (to make sure that it doesn't go into interactive mode or anything) Not to mention again, this would happen whether you rebooted it right after you made them or whether you rebooted it 6 months from then. > Else where is the egg when that "she'll be right mate" > change fails at 9:00am on Monday morning and you've slept in ? echo -n in your startup scripts works wonders :-) > > There is so much more to serious system admin (from your personal desktops > to mainframes) than just applying (security) patches and keeping it running > with no downtime. Well, that is when you don't have hot-swap everything :) > > None of my personal boxes have uptimes that ever exceed 6 months, even my > servers, but I have complete confidence in them rebooting and services being > restarted (modulo file system damage from an unclean shutdown). softupdates should take care of this, and as far as HD trouble, if you're system is really that important then mirror your disks. Cheers, -JD- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004201c0c783$7fe71df0$4904a8c0>