* Re: [gentoo-user] When to reboot after updates to the system
@ 2006-04-29 0:55 99% ` Kevin
0 siblings, 0 replies; 1+ results
From: Kevin @ 2006-04-29 0:55 UTC (permalink / raw
To: gentoo-user
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/._cfg0000_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/._cfg0000_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
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2006-04-29 0:42 [gentoo-user] When to reboot after updates to the system Kevin
2006-04-29 0:55 99% ` Kevin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox