This machine was a "ghost ship." It's use had long come and gone and people had moved their stuff off onto new machines. It was running 32bit RHEL 5.5 no patches, no nothing. It was a security risk at this point. To Mike's point, unless there's good change control, you run the danger of having a machine that's not ever going to reboot sensibly.

A couple years ago I stumbled upon a linux box that was running an ancient version of mysql.. the database was up, but it was running out of a directory like /u01/mysql/bin

The disk /u01 was LONG gone.. but the database continued to run.. it's data was being written off on to a different disk and things worked.. but it was clear that machine would never had rebooted.

Tim.

On Thu, Apr 21, 2022 at 10:06 AM Michael Voorhis via WLUG <wlug@lists.wlug.org> wrote:

Additionally if you never reboot, how do you know the machine WILL
reboot? How do you know what the system will do after a power failure,
etc? Fate will intervene at some point and force you to reboot whether
you want to or not, so you should be prepared with the knowledge of how
the system will respond to that.

On 4/21/22 09:54, David Glaser via WLUG wrote:
> It you kept it up all of the time, how would you apply updates that
> require a re-boot?

_______________________________________________
WLUG mailing list -- wlug@lists.wlug.org
To unsubscribe send an email to wlug-leave@lists.wlug.org
Create Account: https://wlug.mailman3.com/accounts/signup/
Change Settings: https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/
Web Forum/Archive: https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/2CNXUVDBFQA6P6YFSFJPVE4PQVZR3A6A/