Well and there is another good point, I had recently performed an emerge -ud --world on this server and had not rebooted, as well as installed and uninstalled numerous other packages. It probably was a good idea at least in this instance to reboot. Bringing Apache2 down and back up without using graceful probably would have fixed the issue, but it is best to make sure the danged thing will reboot, especially considering that one of my other servers, due to a custom hardware conflict issue that conflict with the kernel will not reboot remotely and only comes back up if someone physically walks into the datacenter and pushes the power button.
On 3/13/06, Gabriel Gunderson <[EMAIL PROTECTED]> wrote: > On Mon, 2006-03-13 at 19:16 -0700, Steve wrote: > > Anyways good lesson, when in doubt reboot > > I don't know. Rebooting is generally a bad way to go about it. What > did rebooting do that you couldn't do yourself? If one doesn't know, > then they missed an opportunity to learn. There is almost nothing that > requires a full reboot outside of a kernel update. > > It took almost a full year of being free from Windows before I actually > started to believe it. The only reason I reboot servers anymore is to > make sure they will boot-up and run as expected in the event they are > automatically rebooted (for whatever reason). > > Just my 2 cents. > > -- > Gabriel Gunderson > http://gundy.org/ > > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
