• 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: place a LaunchAgent on the filesystem, but prevent it from loading unless a boolean key is True
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: place a LaunchAgent on the filesystem, but prevent it from loading unless a boolean key is True

  • Subject: Re: place a LaunchAgent on the filesystem, but prevent it from loading unless a boolean key is True
  • From: Conor Schutzman <email@hidden>
  • Date: Sat, 30 Nov 2013 19:16:39 -0800
Why not just build the logic into the script the agent calls?  Something like an exit call if a file is present.  The agent would load all the time, to “turn it on” you would just delete the file.

Similarly, if there is some criteria for which computers should have this enabled or not, than just use that as the logic break.  This could be as straight forward as a group the user is in, an IP address range, a file buried on the computer somewhere, etc.  I don’t know enough about your spec, or the environment you’re building for to determine the best logic path.

On Nov 30, 2013, at 6:19 PM, Allen Hancock - Watchman Monitoring <email@hidden> wrote:


We're preparing to release an option SupportMenu item, managed via /Library/LaunchAgent.  It'll be enabled for a computer, or disabled, as our Subscriber chooses.



Im trying to figure … what's the less of all evils:

 - Distributing the LaunchAgent as Disabled, then having the postflight set the Disabled key to False as required.

or  

 - omitting it from the BOM and having the postflight copy it into place as required.


It's not the worst abuse of the "package, don't write" guideline, but still, if I can avoid it, I'd like to.


Is there another option, outside of having two versions of the installer?


I suppose I could have the Menu Item look for a key, and launchctl unload itself , but then the app opens for a moment at every login.. seems worst of all these options….


Thanks in advance for any options I'm not seeing.

-- 

Allen Hancock - Watchman Monitoring - A consultant's best friend 

+1-408-352-6145

Help articles at http://support.watchmanmonitoring.com
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
  • Follow-Ups:
    • Re: place a LaunchAgent on the filesystem, but prevent it from loading unless a boolean key is True
      • From: Conor Schutzman <email@hidden>
References: 
 >place a LaunchAgent on the filesystem, but prevent it from loading unless a boolean key is True (From: Allen Hancock - Watchman Monitoring <email@hidden>)

  • Prev by Date: place a LaunchAgent on the filesystem, but prevent it from loading unless a boolean key is True
  • Next by Date: Re: place a LaunchAgent on the filesystem, but prevent it from loading unless a boolean key is True
  • Previous by thread: place a LaunchAgent on the filesystem, but prevent it from loading unless a boolean key is True
  • Next by thread: Re: place a LaunchAgent on the filesystem, but prevent it from loading unless a boolean key is True
  • Index(es):
    • Date
    • Thread