site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Hi Sorin, On Feb 11, 2008, at 11:41 AM, Sorin Negoita wrote: [...] -Dave _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Another solution is to replace all files at startup using a script or another launchd daemon, but I must be sure that this one will be executed before the execution of my daemons and agents. I couldn't find in the launchd documentation any information to make this possible, something like Startup items dependencies or MoveFileEx function from Windows. Maybe I've missed something :( Does it really matter? Inform the user that the first reboot will boot and update some files then reboot again. This way you ensure the daemons are reloaded. Just add a reboot to the end of your update script. Or alternatively don't reboot but instead force a relaunch of all of your daemons after you update the files. The launchctl command should be able to do this. Be careful though with your argument quoting when you do updates using commands in a shell script. Another option is to replace the files the usual way (as part of the update) then restart all of the daemons and agents from your post install script. This way you don't need to have the user reboot at all which is much much nicer, particularly if this is a server-related product. You may also even shut down the daemons and agents pre- install and start them up again post-install. I'm not sure that a MoveFileEx equivalent is really desirable. You know better than Apple ever could what specific needs your daemons have. This email sent to site_archiver@lists.apple.com