NO MORE UPDATES TO THIS PAGE PLEASE. SUBMIT ALL FUTURE COMMENTS TO

5.1.2 pg 96

Your comment about the Windows registry isn't entirely accurate. Changes made to the registry are not necessarily immediate. The registry is simply centralised configuration storage with APIs provided for manipulating it. It's up to the service to determine whether to check for changes. eg if you change some of the "server" configuration settings you will need to reboot before they take effect. Where Microsoft did well was in providing guidelines for things like Services, where you can define dependencies, and then provided a user interface that will manipulate the registry and stop/start the service as required. More modern Unixes have similar command manipulation (eg RedHat^? has "chkconfig" to add/remove rc scripts, and "service" to start/stop daemons; Solaris 10 has it's convoluted service manager which replaces rc scripts and inetd and others so "svcadm disable ssh" with disable ssh from starting up and stop the current ssh daemon). It's also not that much different in concept to modifying inetd.conf or sendmail.cf or smb.conf and sending the appropriate daemon a SIGHUP.

It's still good advice, though, to schedule a reboot after messing around with rc scripts

[ Tom's reply: Fixed. Status: DONE. ]

-- StephenHarris - 11 Aug 2006