<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2800.1276" name=GENERATOR></HEAD> <BODY> <DIV><SPAN class=363193123-12012004><FONT face=Arial size=2>With MS Windows, it seems a reboot is required after nearly every software update.</FONT></SPAN></DIV> <DIV><SPAN class=363193123-12012004><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=363193123-12012004><FONT face=Arial size=2>One of the things I like about UNIX/Linux is the overall design of things such that reboots are not really part of the "problem resolution process".</FONT></SPAN></DIV> <DIV><SPAN class=363193123-12012004><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=363193123-12012004><FONT face=Arial size=2>If I use up2date to get a new httpd update, after it's installed I restart the httpd daemon.... similar for sshd updates etc.</FONT></SPAN></DIV> <DIV><SPAN class=363193123-12012004><FONT face=Arial size=2>For a kernel I reboot the whole machine....</FONT></SPAN></DIV> <DIV><SPAN class=363193123-12012004><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=363193123-12012004><FONT face=Arial size=2>But, how do I know what needs to be restarted/rebooted when updates to things like cron or glibc are installed? To "be safe" I could always reboot the machine after installing updates, but that seems unnecessary and certainly unwanted.</FONT></SPAN></DIV> <DIV><SPAN class=363193123-12012004><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=363193123-12012004><FONT face=Arial size=2>Thanks,</FONT></SPAN></DIV> <P><FONT size=2>Don Russell</FONT></P> <P><FONT size=2>(North America: Pacific Time Zone)<BR><BR><FONT face="Courier New"> \|/<BR> (. .)<BR> ___ooO-(_)-Ooo___</FONT></FONT></P> <P><FONT size=2><FONT face="Courier New"> <BR></FONT><BR></P></FONT> <DIV> </DIV></BODY></HTML>