On Tue, 08 Nov 2005 09:03:32 +1000, Stuart Low said: > Well, if you have a customised kernel you'll probably find that your > need to reboot with a new kernel becomes fairly low (Kernel level > exploits are fairly rare, especially remote ones). > > If you've upgraded services probably the easiest way to ensure they're > loaded with the latest version would be to drop the system to single > user mode then bring it back up to multiuser mode (ala, init 2, init 3).
Or, if you're able to identify "I only applied an Apache patch", you may very well be able to only restart that one service. For RedHat/Fedora systems, you'd do this with 'service httpd restart' (or replace httpd with the name of the /etc/init.d script that starts/stops the service in question). For other systems, you should be able to find a similar "stop then restart" for the specific daemon in question.
pgpx9pCQNMb3W.pgp
Description: PGP signature
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
