site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:subject:from:to:message-id :in-reply-to:mime-version:content-type :content-transfer-encoding; s=smtpout; bh=OvhY+Log4GcJ25gLQftS5t 8Am/s=; b=IWSUhcUPFT6Rk+c+WQNsaMgOxvGJL0jWte5JUyS8tyZQqPFoC1gAlh qZW7CsFCJ8hGsRyjz/DOZVvAgTO/jI/DwH9JeGHQwLmnzfIcbrf+RKOYtsIgiKJN YCDvsNDzr4O+8P0NK5wIjZxXIe54uhO/bNeGrq89ZblR1JL9KEosc= Thread-topic: Upgrade a LaunchDaemon and/or Agent User-agent: Microsoft-MacOutlook/14.13.0.110805 I am dealing with a potential upgrade scenario for an installer package including both a LaunchDaemon and a system-wide LaunchAgent. I want to be prepared for it before the actual upgrade becomes a necessity. Is anyone aware of whether Installer or Launchd manage the replacement of these plists and their associated executables if the jobs are already running? I am particularly interested in the situation for LaunchDaemons. Should I be creating an installer preflight (for example) to unload these launchd jobs first, before the relevant plists and executables are replaced by the package payload? Will unloading the jobs be sufficient to allow the successful upgrade/replacement of the plists and executables? If the jobs were running prior to the upgrade, will the previously-running versions still be running without any scripted intervention on my part -- or logout/reboot? If this is documented canonically, I have missed it. I am most interested in what works for Leopard, Snow Leopard, and Lion clients. Thanks! -- Jeremy _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com