Using SystemStarter seems pretty neat; however, reading through the documentation that Chris mentioned raises at least one question for me. Since SystemStarter is a legacy approach, how does one assure that the daemons run via the new in Panther /etc/mach_init.d and /etc/mach_init_per_user.d approach get restarted appropriately after a system update? Just running sudo SystemStarter restart won't get such services as MirrorAgent, lookupd, configd, etc. restarted. It sounds as though one has to either reboot or look through the bom file that came with the updates to determine which components were updated. If the daemon is handled through the new mechanism then the sudo kill -HUP <daemon> approach needs to be done, as best I can tell. Thanks for any additional info! Norm Norman Cohen nacohen at mac.com "I have such poor vision I can date anybody." Garry Shandling On Sep 26, 2004, at 9:36 AM, Chris Olson wrote: > On Sep 26, 2004, at 8:16 AM, Peter Krug wrote: > >> But how do you know for sure which subsystems were affected and which >> programs to restart? Or should I RTF man pages? They always seem to >> confuse me - sample commands explaining the variables would be real >> helpful for me. > > The documentation is fairly thorough on which systems are affected > just by reading the supporting information on Apple's website > regarding the update. If it's at all confusing, I'd recommend the > reboot option until you get a better handle on BSD systems in general, > the Darwin system in particular, and understand how the init system > works. > > Perhaps this link to the ADC documentation would be helpful: > http://developer.apple.com/documentation/MacOSX/Conceptual/ > BPSystemStartup/Tasks/ManagingStartupItems.html > > --