• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: making an installed application run at startup
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: making an installed application run at startup


  • Subject: Re: making an installed application run at startup
  • From: "Adam Fisk" <email@hidden>
  • Date: Tue, 13 Jan 2009 22:34:54 -0800

You almost definitely want to use launchctl.  I'm also wary of running
any application on startup, and I'm moving my own app away from this
behavior.  The cleanest way to do it is with launchctl/launchd though.
 This behavior is commented out from my postflight, but you can check
out:

http://svn.littleshoot.org/svn/littleshoot/trunk/install/osx/LittleShoot/extras/postflight

There's also super handy error reporting in there using curl --
basically catches any errors in the script and reports them to my
servers.

You want to put your plist in ~/Library/LaunchAgents and call launchctl load.

-Adam


On Tue, Jan 13, 2009 at 4:50 PM, Jason Proctor <email@hidden> wrote:
> in the installer project i'm looking at, there are two items which are both
> applications installed into /Applications.  i would check the box for one of
> them and not the other.
>
> i'm just being flippant about the one checkbox thing, but IMHO this would be
> a good area for the Installer to help out. some applications can
> legitimately need to start at login, and all the solutions proposed here
> have drawbacks - from messing up a previously good loginwindow.plist, to
> having something start at launch for a user who didn't install the
> application.
>
>
>
> At 4:42 PM -0800 1/13/09, Greg Neagle wrote:
>>
>> How would PackageMaker know which executable to launch at login from a
>> simple checkbox?  Your installer could install several executable items.
>>
>> I agree that PackageMaker could help, but I'm not convinced it would be
>> and easy addition to PackageMaker, or that Apple should encourage developers
>> to easily add things to the LoginItems.  I have enough things launching at
>> login that I didn't ask for...
>>
>> -Greg
>>
>> On Jan 13, 2009, at 4:30 PM, Jason Proctor wrote:
>>
>>> all this could have been avoided by a checkbox in PackageMaker. then the
>>> Installer could ask the user whether it's OK to do it, etc. this is a simple
>>> requirement that has been massively overcomplicated -- IMHO.
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Installer-dev mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>



--
Adam Fisk
http://www.littleshoot.org
read my blog at: http://adamfisk.wordpress.com
follow me at: http://twitter.com/adamfisk
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: making an installed application run at startup (From: Karl Kuehn <email@hidden>)
 >Re: making an installed application run at startup (From: Greg Neagle <email@hidden>)

  • Prev by Date: Re: setting status from postflight
  • Next by Date: PackageMaker install/upgrade on 10.4 vs 10.5
  • Previous by thread: Re: making an installed application run at startup
  • Next by thread: InstallationCheck script is getting its executable bit reset
  • Index(es):
    • Date
    • Thread