launchd

I encounter a strange situation in a launchd managed daemon when I try to sleep in the SIGTERM handler that is managed with Grand Central Dispatch as described here . Everything works fine and I do get a SIGTERM signal handler before receiving a SIGKILL when I do not sleep in the SIGTERM handler. But as soon as I do sleep -- even for extremly short amounts of time like a usleep(1); -- I do not get a SIGTERM handler at all but instead my daemon is SIGKILLed instantly by launchd. Btw I am using EnableTransactions in my plist file and the proper vproc_transaction_begin(3) / vproc_transaction_end

I would like to launch a shell command when a specific external bluetooth device is connected to my Mac. A nice way (without installing third party software) to do that is by adding a plist file in ~/Library/LaunchAgents On this page , there is an example of launching an event when the wifi connects to a specific location. It is done by watching a specific file : <key>WatchPaths</key> <array> <string>/Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist</string> </array> Do you think it'd possible to do the same with bluetooth events ? Thanks for your help ! iero Create

Since startup items and rc commands are both deprecated (and in many cases not working at all) on OS X in favour of launchd , I'd like to find out what the correct way would be to setup a shell script that runs on logout/shutdown. For a startup item it was possible to create a shell script that looked something like: #!/bin/sh StartService() { echo "Started." } StopService() { echo "Stopped." } RunService "$1" But the RunService command isn't supported when running a script from launchd , and I'm not sure it's meant to be used anymore anyway. If possible, I'd like to create a shell script that

EDIT: It appears as if I am getting an error in the console com.apple.launchd: (com.xxxx.adbind[57]) Exited with code: 1 What does that even mean? Also; if I load the launchd plist file logged in by using the launchctl command it works fine! I'm driving myself crazy trying to figure out why my launchd is not working. I'm using this in Mountain Lion 10.8.2 When I manually start it using launchctl it says it's loaded, but the script is not running. The script when ran manually works fine as well. Perhaps it just needs a better set of eye's to look at what I'm doing. First, I'll explain what it

I have a shell script that I run in launchd that backs up my MAMP MySQL install. Unfortunately if MAMP isn't running it throws an error and sends it to internal mail. I want any errors to be ignored (sent to /dev/null ), but if there isn't an error, to continue on. I have attempted the following, which correctly creates the backup when MAMP is running, but sends mail if it's not running (stderr): #!/bin/bash /Applications/MAMP/Library/bin/mysqldump --opt -u root -pPASSWORDHERE --host=localhost --all-databases > | gzip -9 > /Users/Paul/Dropbox/Development/Shared\ DBs/BACKUPS/all_databases_-

I'm trying right now to create separate user for jenkins on Mac Os and run it with this user. I've created a new user: # Create the group sudo dscl . create /Groups/jenkins sudo dscl . create /Groups/jenkins PrimaryGroupID 300 # Create the user sudo dscl . create /Users/jenkins sudo dscl . create /Users/jenkins PrimaryGroupID 300 sudo dscl . create /Users/jenkins UniqueID 300 sudo dscl . create /Users/jenkins UserShell /bin/bash # Set the users pasword sudo dscl . passwd /Users/jenkins 123qweASD # Add the user to the group sudo dscl . append /Groups/jenkins GroupMembership jenkins And the I