Haven't rebooted Ubuntu server in 4-months with updates. This okay?
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Mac OS X Leopard 10.6.2, Windows 2003 Server/Vista/7/XP/2000/NT/98, Ubuntux64, CentOS4.8/5.4
Posts: 2,986
Rep:
Haven't rebooted Ubuntu server in 4-months with updates. This okay?
I'm usually familiar with the Windows world of doing updates and then having to reboot the machine for the updates to take effect. Is this the same case with Linux servers? I can understand if it's a new kernel, but I'm getting updates to things like DNS, SSH, SAMBA, some library files, tar, etc... I see that for some of the services the system stops and restarts the service, so I'm assuming the new updates are in effect? My users are running files on the server 24/7 so I can't really reboot it without giving them waaaay advanced notice, and usually they are finicky about that since they hate to have their jobs interrupted.
There is no need to reboot a Unix server unless you have updated/changed the kernel (and there are even ways to avoid that by booting another kernel from inside of the running one). Once you have installed the updates, the daemons should either restart themselves, or at the very least will be running the new version once the next request comes in from the client side (depending on which service we are talking about).
Distribution: Mac OS X Leopard 10.6.2, Windows 2003 Server/Vista/7/XP/2000/NT/98, Ubuntux64, CentOS4.8/5.4
Posts: 2,986
Original Poster
Rep:
What if the update has no service associated with it? For example, TAR. It will just replace the TAR binary and associated files and the next time I run TAR it will be the new and updated version?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.