On Thu, 2002-10-10 at 08:54, juaid wrote: > From: "Sean Millichamp" <[EMAIL PROTECTED]> > > > I've done it with dozens of servers and it works. I remote admin a > > number of single-server environments and have upgraded them all from 7.1 > > or 7.2 to 7.3 using apt with great success. > > that's great! :)
A couple more notes for the list archives on this in case anyone feels like trying it, mostly from the perspective of a remote upgrade. If I was local I'd probably use the CDs. 1) If you are doing a remote upgrade I noticed that the box stops accepting SSH connections until sshd is restarted. You may want one or more connections open to the box in case one dies. If you lose all connectivity mid-way you are stuck going to the console. 2) I always rebooted immediately after performing the post-upgrade cleanup: making sure GRUB was set, merging in any critical looking changes in the *.rpmnew/*.rpmorig/*.rpmsave files, etc). Presumably you could keep running without a reboot but some things (like sshd) are weird after. 3) You can run the upgrade while the box is up but I would not recommend doing so while it is in active use with complicated apps/servers (such as people actively using Samba) 4) If you use dynamic routing (I use zebra on a few boxes) be aware that a lot (all?) of the RPM upgrades result in daemon restarts. Be VERY sure that none of the restarts you see will cause you to lose connectivity if you are coming in remotely. As I said above, losing connectivity is bad. 5) This should be obvious, but you should really test this on a non-production box first to get comfortable with the procedure. Sean -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
