[gentoo-user] When to reboot after updates to the system
Hi All- I've read the portage documentation at http://www.gentoo.org/doc/en/index.xml?catid=gentoo and I've searched and browsed the gentoo-user mailing list archive, but I have a question that I don't see answered anywhere. It seems to me that it must be true that sometimes, after a system upgrade done with: emerge -uD system or emerge -uD world I must reboot the computer for the changes to take effect. I could be wrong on this, but it seems reasonable to me to think that I should reboot in certain circumstances. Perhaps after an upgrade to the glibc package or other libraries... not sure. Am I right about this? If so, can someone tell me under exactly what circumstances I should reboot immediately after a system update such as these above? (ie. if glibc gets updated, if you add a new USE flag that requires recompiling certain packages, after an update to the sysvinit package, etc.) I realize of course that if I compile a new kernel and want to use the new kernel then I need to configure the boot manager and reboot with the new kernel, but it seems to me that there would be other circumstances aside from this that would require a reboot after a system update. Thanks for any replies. -Kevin -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] When to reboot after updates to the system
You've been hanging around Windows users too much G. Linux normally doesn't require a reboot. Sometimes you have to restart the deamons with the /etc/init.d/whatever restart. On Friday April 28 2006 20:42, Kevin wrote: Hi All- I've read the portage documentation at http://www.gentoo.org/doc/en/index.xml?catid=gentoo and I've searched and browsed the gentoo-user mailing list archive, but I have a question that I don't see answered anywhere. It seems to me that it must be true that sometimes, after a system upgrade done with: emerge -uD system or emerge -uD world I must reboot the computer for the changes to take effect. I could be wrong on this, but it seems reasonable to me to think that I should reboot in certain circumstances. Perhaps after an upgrade to the snip -Kevin -- Brett I. Holcomb -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] When to reboot after updates to the system
On a related note, what is the most correct procedure for restarting a service after an update to a service (say named or cyrus-imapd or apache or sshd)? I've been doing something like this: # emerge -v openssh examine config file differences and make any adjustments that are required to be done by hand. # /etc/init.d/sshd stop # mv -i /etc/init.d/._cfg_sshd /etc/init.d/sshd # /etc/init.d/sshd start But I've noticed that there are cases when this general procedure doesn't work. Perhaps because binaries change location between package versions and the old /etc/init.d/service script presumes the old package binary location and the new package has already been installed so the new binaries are no longer with the old startup script thinks they are. In those cases, I usually find the service with ps and kill it by hand, then zap the service and start it again, using the new start script, but maybe there's a better way. Seems to me that it might be better to do something like this: # /etc/init.d/sshd stop # emerge -v openssh examine config file differences and make any adjustments that are required to be done by hand. # mv -i /etc/init.d/._cfg_sshd /etc/init.d/sshd # /etc/init.d/sshd start But if I'm remotely logged in to the box using ssh, then this has some obvious problems (my connection to the box goes down when I turn off the sshd daemon). Any thoughts on this issue? -Kevin -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] When to reboot after updates to the system
Kevin wrote: Hi All- I've read the portage documentation at http://www.gentoo.org/doc/en/index.xml?catid=gentoo and I've searched and browsed the gentoo-user mailing list archive, but I have a question that I don't see answered anywhere. It seems to me that it must be true that sometimes, after a system upgrade done with: emerge -uD system or emerge -uD world I must reboot the computer for the changes to take effect. Nah, you can restart pretty much any service to get the new version going. Technically you shouldn't ever have to reboot except kernel updates. (We aren't running windows here) ;) HTH, (unofficial advice) -Jeremy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] When to reboot after updates to the system
Kevin wrote: Hi All- I've read the portage documentation at http://www.gentoo.org/doc/en/index.xml?catid=gentoo and I've searched and browsed the gentoo-user mailing list archive, but I have a question that I don't see answered anywhere. It seems to me that it must be true that sometimes, after a system upgrade done with: emerge -uD system or emerge -uD world I must reboot the computer for the changes to take effect. I reboot if I need to install or change hardware. As far as updates go, you may have to reboot after compiling a new kernel. I think that I may have read somewhere how to change kernels without rebooting, so you may not even need to reboot for any software. -- Phil My Home Page: http://fancypiper.info/ Our 2nd CD: http://www.cdbaby.com/naomisfancy/ Naomi's Fancy: http://www.naomisfancy.net/ Free tunes: ftp://http://fancypiper.info/ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] When to reboot after updates to the system
You need to run etc-update (or one of it's cousins) if you are told files need updating. After that run the /etc/init.d/sshd restart. On Friday April 28 2006 20:55, Kevin wrote: On a related note, what is the most correct procedure for restarting a service after an update to a service (say named or cyrus-imapd or apache or sshd)? I've been doing something like this: # emerge -v openssh examine config file differences and make any adjustments that are required to be done by hand. # /etc/init.d/sshd stop # mv -i /etc/init.d/._cfg_sshd /etc/init.d/sshd # /etc/init.d/sshd start But I've noticed that there are cases when this general procedure doesn't work. Perhaps because binaries change location between package versions and the old /etc/init.d/service script presumes the old package binary location and the new package has already been installed so the new binaries are no longer with the old startup script thinks they are. In those cases, I usually find the service with ps and kill it by hand, then zap the service and start it again, using the new start script, but maybe there's a better way. Seems to me that it might be better to do something like this: -- Brett I. Holcomb -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] When to reboot after updates to the system
On Saturday 29 April 2006 02:42, Kevin wrote: It seems to me that it must be true that sometimes, after a system upgrade done with: emerge -uD system or emerge -uD world I must reboot the computer for the changes to take effect. short answer: no long answer: only after kernel updates I could be wrong on this, but it seems reasonable to me to think that I should reboot in certain circumstances. Perhaps after an upgrade to the glibc package or other libraries... not sure. you are wrong. You don't need to reboot. Only, and really only after a kernel update you need to reboot. Services might to have to be restarted, but that requires no reboot, just a console and root. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] When to reboot after updates to the system
On Friday 28 April 2006 20:04, Phil Sexton [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] When to reboot after updates to the system': Kevin wrote: Hi All- I've read the portage documentation at http://www.gentoo.org/doc/en/index.xml?catid=gentoo and I've searched and browsed the gentoo-user mailing list archive, but I have a question that I don't see answered anywhere. It seems to me that it must be true that sometimes, after a system upgrade done with: emerge -uD system or emerge -uD world I must reboot the computer for the changes to take effect. I reboot if I need to install or change hardware. As far as updates go, you may have to reboot after compiling a new kernel. I think that I may have read somewhere how to change kernels without rebooting, so you may not even need to reboot for any software. Theoretically it's possible just by writing to /proc/kmem -- IIRC, that was one of the reasons it was writable: so you could apply (binary) patches against a running kernel. I've never seen any non-malware that does so. There is a GPL'd proof-of-concept rootkit that will hide its existence by modifying /proc/kmem. (The rootkit doesn't actually do anything malicious and you have to have root access to modify /proc/kmem; the rootkit was just showing how to do this trickery without loading a module) There's also the new kexec feature option in mm kernels (and it might have come mainline) that allows the kernel to start another kernel instead of rebooting your hardware. That's basically as bad as a reboot anyway, because all services come down and all users are kicked out -- it is faster though, because you don't go down to the bootloader/BIOS level. I found it (or my hardware) was a little bit buggy. My USB drivers would only work every other kexec. Since I use a USB keyboard, this wasn't a workable solution. -- If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability. -- Gentoo Developer Ciaran McCreesh pgpwabKSMiqJ4.pgp Description: PGP signature
Re: [gentoo-user] When to reboot after updates to the system
Hemmann Volker Armin wrote: Only, and really only after a kernel update you need to reboot. Perhaps not even then. http://www-128.ibm.com/developerworks/linux/library/l-adfly.html -- Phil My Home Page: http://fancypiper.info Our 2nd CD: http://www.cdbaby.com/naomisfancy Naomi's Fancy: http://www.naomisfancy.net/ -- gentoo-user@gentoo.org mailing list
