Date: Mon, 25 Jan 1999 11:04:31 -0000 From: paul@originative.co.uk To: jkh@zippy.cdrom.com, jb@cimlogic.com.au Cc: peter@netplex.com.au, nsouch@teaser.fr, dillon@apollo.backplane.com, cvs-committers@FreeBSD.ORG Subject: RE: CVS totally broken on freefall Message-ID: <A6D02246E1ABD2119F5200C0F0303D10FDD8@OCTOPUS>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: Jordan K. Hubbard [mailto:jkh@zippy.cdrom.com] > Sent: Sunday, January 24, 1999 11:20 PM > To: John Birrell > Cc: peter@netplex.com.au; nsouch@teaser.fr; > dillon@apollo.backplane.com; > cvs-committers@FreeBSD.org > Subject: Re: CVS totally broken on freefall > > > > This is a *VERY* good example of what not to do on a > production system. > > People should know better. Grrr. > > You know of a better way of upgrading machines? If so, tell me now > before we do hub. :) > > I don't have full spares for each, so I can't do the old roll-over > from a hot spare trick. If this were a commercial shop I'd have one > or two super-spares in the corner, sure, but project funds are not > quite so abundant. :) That's fair enough, this isn't a commercial setup and some corners get cut but there are still some things that definately should have been done. 1) Schedule the upgrade and warn people about it. 2) Get a checklist of what services run on the machine and make sure they're going to still work afterwards. 3) Disable critical services, like cvs, while the upgrade takes place to prevent any mishaps 4) Disable logins while you're actually doing it so people don't do things in the middle of the upgrade. 5) Take a backup before starting. 6) Actually announce that it's taking place so everyone doesn't run around trying to work out why things have stopped working. The above steps just take organisation and would have prevented the cvs problems and the perl script problems that occured. Who knows what else might still fall out in the wash. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A6D02246E1ABD2119F5200C0F0303D10FDD8>