March 2011 - Installer-dev - lists.apple.com

problems running packagemaker from shell script
by Nat Echols 31 Mar '11

31 Mar '11

site_archiver(a)lists.apple.com Delivered-To: Installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=ZO9qVtvV+mKiYoHZIW3wa8y5THUIS0k4bzmTQkKJ5SE=; b=XKWJ4ig19a+GnKSzgtn5/7V7xk7jJrPv6aSNYDBDP3zh7RTxaALQ7Xced5s+I9+NNw QO8IcAriiebi30YzgKpW23ChtvZGUOuBrcvZhuiLpk0Qivu6VhCdSf8o/3OJd3TfRui1 ADQi6C+SFciG7Ml3TCpn6rIybV97qS9d6OvYA= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=MjAkGSn+Jqw3ovtc6W/WGx95lhy6AJ8ZZ+wHN5Sodu9Tic3QmjyjPlStX2vbWnycUP 6ua+mN83Zpst644rLJCmJex87xmMxFbZLLpnF9+UEzH3w/p5Io5OHe6BS5hkhL4h+rw1 UEXhmk1eMfMQD5YNPaX7MTa7pW1KlNzfLjyc4= _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Option to execute a command?
by Allister Banks 31 Mar '11

31 Mar '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Option to execute a command?
by Karl Kuehn 31 Mar '11

31 Mar '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to:x-mailer; bh=VmMPCKvermUF651tcupxp4qMFjfa2oAnMDrzpib+fWg=; b=RmiGmGWuraMKdY9TPloYrD9IpdepjK+G75h/us1Ri2fz8twDibMNT1yRcnKvt/E0se oScnNFh4JzIdW8J28YKPV66PIMrlE6R16jTRTY3vT7zvva6EORe4EafQeKupCm6oE5dr JTImM3sPNDqq2JfTV6si1obnE0ip0iEewdVr0= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; b=AnOSN2bXw8pT7UcWRiWuamiAjfZ1Qn8cZnTAzv8m6AzSDliFA7gFLwpKOvl52el6Ph wGAHzJSPbvcxnpAoXUo7Y4DHmWy/R4HhTyCHleO75rAolnpSE8c32tQx9mfjCtb+SA65 y3L4bX6xSnDx6AgjdWtgM6j656Lqpq5oFj0is= _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Option to execute a command?
by Stephane Sudre 31 Mar '11

31 Mar '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=I/xQzvnqG1FiVcC6bOgcqxSNMOHz49k0y0qNM6n3dOI=; b=pNuGGEE+5KVx/iPY2N1idrPE/NOEe34zxwyKYNIPxoHUEv3DvuQ2YLlNuyMPGg3NCm WKJQRk3Yn3uuaMghgj5NM+RUQXDPfKxUjTyvovTBgnXa2YV/2RJ67Bl8JiEebMEjHAKa HF9pAGbbgyqrcWg1kJGpXBmATsGxgscRJJq0w= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Y6kd/PlvHAEEP0QI0Xc2EKfiIFiqo7Lx7InqR3qRgK497M4Ec/b7+LkkQiww1nM1cq 0KHqalVyrW1C5C6R+RAmtO5H6acBcWQDLLty895DPvzJZp8UCfuHD4icPf0FBdRKQ9Qp ZShqQ7vPQ2ZI30qtWoBFTdb5SLyH7DOSX8CQ8= Another solution is to only allow the package to be installed on the startup disk. On Wed, Mar 30, 2011 at 9:11 PM, Karl Kuehn <kuehn.karl(a)gmail.com> wrote: > One thing that is missing in this conversation is that you could be running > this installer targeted at a volume other than the boot volume. It is really > simple to catch this case, so we should always be pushing people to do this > when they write installer scripts. More inline: > On Mar 30, 2011, at 11:36 AM, Greg Neagle wrote: > > preinstall: > > #!/bin/bash > > LAUNCHD=/Library/LaunchDaemons/edu.caltech.autonomy.foo.plist > > if [ -e "$LAUNCHD" ]; then > > launchctl unload -w "$LAUNCHD" > > fi > > This unloads the launchd job defined in > /Library/LaunchDaemons/edu.caltech.autonomy.foo.plist only if it already > exists. This is useful for reinstalls and installs of new versions of your > software. The file does not need to exist. > > Here you should be checking if the target volume is '/'. This is simple in > this case, just replace the appropriate line with this: > if [ -e "$LAUNCHD" ] && [ "$3" == "/" ]; then _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Option to execute a command?
by Per Olofsson 31 Mar '11

31 Mar '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AQHL7kJU1BT4POw5L0OnxLhGDUmecpRFVkuAgACuEoCAAAIlgIAAC5aAgAACpgCAAAnaAIAAD+sAgAC4C4A= Thread-topic: Option to execute a command? 30 mar 2011 kl. 22:08 skrev Nathan Sims: > Thanks Karl, Greg, and Per. I am much farther along now. > > When I run my build package, the installation fails due to not being able to run the pre and post scripts: > > installd[2326]: PackageKit: Executing script "./preinstall" in /private/tmp/PKInstallSandbox.d9BoJ7/Scripts > installd[2326]: ./preinstall: launchctl: Error unloading: edu.caltech.autonomy.foo > . . . > installd[2326]: PackageKit: Executing script "./postinstall" in /private/tmp/PKInstallSandbox.d9BoJ7/Scripts/ > installd[2326]: ./postinstall: launchctl: Dubious ownership on file (skipping): /Library/LaunchAgents/edu.caltech.autonomy.foo.plist > installd[2326]: ./postinstall: nothing found to load > > What ownership is the plist file supposed to have? root:wheel chmodded 0644. Binaries that are executed should also be owned by root, and sit in a root owned directory, otherwise you'll have an easy way to privilege escalation. > All the files have been moved into the correct places on disk by the installer, and the scripts are all +x. If I manually do a 'launchctl load /Library/LaunchAgents/edu.caltech.autonomy.foo.plist' it works, but the installer doesn't seem to like it. Ah, I assumed that you need to load a LaunchDaemon, which executes in the system's context, but you're loading a LaunchAgent, which executes in the user's session. Loading and unloading LaunchAgents for users is notoriously difficult, see: http://stackoverflow.com/questions/1106638/starting-stopping-a-launchd-agen… http://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPS… The easiest way to fix it is to set the Restart Action to Require Logout. -- Per Olofsson System Administrator, ITS, University of Gothenburg _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Option to execute a command?
by Per Olofsson 31 Mar '11

31 Mar '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AQHL7kJU1BT4POw5L0OnxLhGDUmecpRFVkuAgACuEoCAAAIlgIAAC5aAgAACpgCAAAnaAIAAxIAA Thread-topic: Option to execute a command? 30 mar 2011 kl. 21:11 skrev Karl Kuehn: > One thing that is missing in this conversation is that you could be running this installer targeted at a volume other than the boot volume. It is really simple to catch this case, so we should always be pushing people to do this when they write installer scripts. Good catch, and you're probably right about -w too. My reasoning was that if an upgrade fails, you don't want a half-broken install to launch until you have a successful install (which loads -w). So to summarize, the scripts should look like so: preinstall: > #!/bin/bash > > LAUNCHD=/Library/LaunchDaemons/edu.caltech.autonomy.foo.plist > if [ -e "$LAUNCHD" && "$3" == "/" ]; then > launchctl unload "$LAUNCHD" > fi postinstall: > #!/bin/bash > > if [ "$3" == "/" ]; then > launchctl load /Library/LaunchDaemons/edu.caltech.autonomy.foo.plist > fi -- Per Olofsson System Administrator, ITS, University of Gothenburg _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Option to execute a command?
by Nathan Sims 30 Mar '11

30 Mar '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thanks Karl, Greg, and Per. I am much farther along now. When I run my build package, the installation fails due to not being able to run the pre and post scripts: installd[2326]: PackageKit: Executing script "./preinstall" in /private/tmp/PKInstallSandbox.d9BoJ7/Scripts installd[2326]: ./preinstall: launchctl: Error unloading: edu.caltech.autonomy.foo . . . installd[2326]: PackageKit: Executing script "./postinstall" in /private/tmp/PKInstallSandbox.d9BoJ7/Scripts/ installd[2326]: ./postinstall: launchctl: Dubious ownership on file (skipping): /Library/LaunchAgents/edu.caltech.autonomy.foo.plist installd[2326]: ./postinstall: nothing found to load What ownership is the plist file supposed to have? All the files have been moved into the correct places on disk by the installer, and the scripts are all +x. If I manually do a 'launchctl load /Library/LaunchAgents/edu.caltech.autonomy.foo.plist' it works, but the installer doesn't seem to like it. On Mar 30, 2011, at 12:11 PM, Karl Kuehn wrote: > One thing that is missing in this conversation is that you could be running this installer targeted at a volume other than the boot volume. It is really simple to catch this case, so we should always be pushing people to do this when they write installer scripts. More inline: > > On Mar 30, 2011, at 11:36 AM, Greg Neagle wrote: > >>> preinstall: >>> >>>> #!/bin/bash >>>> >>>> LAUNCHD=/Library/LaunchDaemons/edu.caltech.autonomy.foo.plist >>>> if [ -e "$LAUNCHD" ]; then >>>> launchctl unload -w "$LAUNCHD" >>>> fi >> >> This unloads the launchd job defined in /Library/LaunchDaemons/edu.caltech.autonomy.foo.plist only if it already exists. This is useful for reinstalls and installs of new versions of your software. The file does not need to exist. > > Here you should be checking if the target volume is '/'. This is simple in this case, just replace the appropriate line with this: > > if [ -e "$LAUNCHD" ] && [ "$3" == "/" ]; then > > And secondarily I don't understand why you would use the '-w' flag. That is going to have the effect of causing this to never get launched (automatically) again. And remember on 10.6 this flag has moved to separate file. It happens later you are also using the 'load -w', so this will get undone. But it is not needed, and could lead to unexpected side-effects in odd cases. > > >>> postinstall: >>> >>>> #!/bin/bash >>>> >>>> launchctl load -w /Library/LaunchDaemons/edu.caltech.autonomy.foo.plist >>>> >> >> Since this is a postinstall script, the payload has been installed, which presumably includes your launchd plist. >> This script simply tells launchd to load the plist. > > Same change for this, but you only need to test if $3 is what you expect. I also don't think you need the '-w' here either. That would mess with the settings the user may have made. > >> So I don't see why you need the plist file anywhere other than your package payload. > > Agreed. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Option to execute a command?
by Karl Kuehn 30 Mar '11

30 Mar '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Option to execute a command?
by Greg Neagle 30 Mar '11

30 Mar '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Let us assume you are working from Per Olofsson's example. > Start by creating a folder named Scripts, and inside create two bash scripts: > > preinstall: > >> #!/bin/bash >> >> LAUNCHD=/Library/LaunchDaemons/edu.caltech.autonomy.foo.plist >> if [ -e "$LAUNCHD" ]; then >> launchctl unload -w "$LAUNCHD" >> fi This unloads the launchd job defined in /Library/LaunchDaemons/edu.caltech.autonomy.foo.plist only if it already exists. This is useful for reinstalls and installs of new versions of your software. The file does not need to exist. > > postinstall: > >> #!/bin/bash >> >> launchctl load -w /Library/LaunchDaemons/edu.caltech.autonomy.foo.plist >> Since this is a postinstall script, the payload has been installed, which presumably includes your launchd plist. This script simply tells launchd to load the plist. So I don't see why you need the plist file anywhere other than your package payload. -Greg On Mar 30, 2011, at 11:27 AM, Nathan Sims wrote: > On Mar 30, 2011, at 10:45 AM, Greg Neagle wrote: > >> On Mar 30, 2011, at 10:37 AM, Nathan Sims wrote: >> >>> How can I have PackageMaker place the $LAUNCHD plist into the LaunchAgents folder so that launchctl can run it? >>> >> By making it part of your package payload, just like any other file you'd like installed. > > But doesn't the preinstall script get run before any files get moved? > _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Option to execute a command?
by Nathan Sims 30 Mar '11

30 Mar '11

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Mar 30, 2011, at 10:45 AM, Greg Neagle wrote: > On Mar 30, 2011, at 10:37 AM, Nathan Sims wrote: > >> How can I have PackageMaker place the $LAUNCHD plist into the LaunchAgents folder so that launchctl can run it? >> > By making it part of your package payload, just like any other file you'd like installed. But doesn't the preinstall script get run before any files get moved? _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0