- launchd-dev - lists.macosforge.org

Re: [launchd-dev] Run job when network configuration changes
by Christopher Hunt 15 Dec '07

15 Dec '07

Le 5 déc. 07 à 16:04, Jeremy Reichman a écrit : > I would be just as happy if there were a file that was > consistently and > reliably modified during network changes, so that the WatchPaths > key could > be used. I'm not aware of such a file and past discussions about > this on the > MacEnterprise list haven't turned one up (to my recollection), but > that > doesn't mean it doesn't exist. > I've not really been following this thread but, if I were wanting to do this, I think I'd write a little bit of Cocoa to detect network configuration changes and write a file to a location that a launchd job watches. I following a similar strategy for some other launchd based actions. Works nicely. Cheers, -C

1 0

Run job when network configuration changes
by Louis Granboulan 13 Dec '07

13 Dec '07

Dear all, I would like to support Jeremy Reichman's request, because I apparently have similar needs. I have used the Kicker.xml technique to make automatic backups of my laptop. However, this laptop connects to various networks, and should backup only when connected to the ones where enough bandwidth is available. Moreover, one of such networks uses a 802.1x authentication, and I can backup only when authenticated. In that case, I go from a wired- non-authenticated connection to a wired-authenticated connection, and I need to launch the backup script after authentication. Thanks, Louis

8 16

launch cocoa-app (with gui) from launchd
by Bob Kells 12 Dec '07

12 Dec '07

Problem may be resolved. I'm looking at my code that issues the runModal call. My NSAlert object is created within a loop that depends on the number of alerts to display. I was retain/releasing this object within the loop. I noticed that NSAlert is autoreleased, so I removed the retain/release statements, and now I get my alert panels. Again, this worked outside of launchd with the retain/release. But now it appears to be working when launched from launchd. My next step is to skip the script, and call it directly from launchd. I'll let you know the outcome tomorrow...bob

1 0

launch cocoa-app (with gui) from launchd
by bob kells 12 Dec '07

12 Dec '07

I have been unsuccessful so far attempting to launch an xcode cocoa app from launchd. I have tried loading 2 different versions of a plist that reference either the executable, or the .app bundle. Neither works. I noticed a prior listing explaining that the actual exe must be referenced, not the .app bundle. ps shows that the process actually gets created both ways. However, nothing appears. I am able to launch the app successfully from a script file and the cmd-line. But when the script file (which launches the app) is run via launchd, again nothing happens. I am using WatchPaths, and the Program key has been set to either the executable, or the .app bundle. Any suggestions out there? thanks...bob -- View this message in context: http://www.nabble.com/launch-cocoa-app-%28with-gui%29-from-launchd-tp142659… Sent from the Launchd mailing list archive at Nabble.com.

4 3

Configurion a Cocoa app as a user agent
by James Bucanek 10 Dec '07

10 Dec '07

Greetings, I have a Login Item that I'd like to replace with a ~/Library/LaunchAgent. It's a LSUIElement=YES Cocoa application. What should the executable path be? If I set it to the bundle folder, is launchd smart enough to figure out that its an application? Or do I need to set it to .../MyApp.app/Contents/MacOS/MyApp? I ask because I've been warned by the Cocoa engineers to avoid starting applications that way. -- James Bucanek

2 3

Thanks for the WatchPath behavior change
by Jeremy Reichman 05 Dec '07

05 Dec '07

I've also noticed, in the theme of being thankful for changes in Leopard, that the behavior for the WatchPath key is different. I believe that change is for the better. In Leopard, both creating and deleting the watched path results in any job waiting for its modification to fire. This is great -- in Tiger, my experience was that the path always had to exist and that made WatchPath more limited and less useful. One question though: since removing the path also runs the job, is there a way to avoid that specific behavior? To only have the job run if the path is created or is modified in place (without deletion)? I know that that case is probably one where the QueueDirectory key should be used instead, but I figured I'd ask. Again, thanks! -- Jeremy

3 2

Sincere thanks about wake from sleep
by Jeremy Reichman 05 Dec '07

05 Dec '07

I have tested launchd jobs that were scheduled to run during sleep subsequently execute when a system is woken up. I'm happy that missed jobs do now run -- and they run immediately upon wake in Leopard. In Tiger, if the jobs ran, it was hours later. They were greatly offset from the time of system wake. This made the use of scheduled overnight jobs less useful from a systems administration perspective, and Leopard definitely improves upon that experience. Thanks! -- Jeremy

2 1

Cross-job coalescing
by Jeremy Reichman 05 Dec '07

05 Dec '07

I haven't found a way to do this after looking over the docs (but not the new TechNote) ... I am wondering if there is a way to have two or more launchd tasks that call the same script coalesce into the same event during events like wake from sleep. For example, what if the same script is called by both a nightly job, and a weekly job? Are the various instances of the jobs that would have run automatically then coalesced into one instance if their scheduled execution is missed? Or, if not, is there a way to have some other cross-job identifier that is shared by multiple launchd jobs so that the same target script is not run more than once? TIA. -- Jeremy

3 3

The mysterious SHAuthorizationRight key
by Christopher Hunt 03 Dec '07

03 Dec '07

Hi there, Running 10.5.1, I see the following in my syslog: com.apple.launchd[1] (org.apache.httpd): Unknown key: SHAuthorizationRight Upon investigating the launchd plist for httpd there is a declaration: <key>SHAuthorizationRight</key> <string>system.preferences</string> Unfortunately I have been unable to find launchd documentation describing this key. Can you please advise; I like to know what my syslog messages mean. :-) Cheers, -C

2 1

launchctl unload not working
by James Bucanek 30 Nov '07

30 Nov '07

Greetings, I'm having a number of issues with launchd, particularly under Leopard. (Most, if not all, of this works just fine under Tiger.) My current, and most pressing issue, is trying to replace a daemon when the user upgrades their software. Here's what I've got running - A daemon is installed in /Library/LaunchDaemons/QRecallScheduler501.plist. I install the file by writing the plist then executing 'launchctl load /path-to-plist' as root. The .plist file has the UserName property set to an individual user. This has been working (mostly) until I need to upgrade the user's software. I've tried various techniques, but the one I'm using now which I think should work doesn't. Setup (if this makes any difference): The path to the daemon is a symbolic link to the actual binary in my application bundle. When the application is upgraded (via Sparkle), the application bundle is replaced with the new application bundle containing an updated daemon. Step #1: Run 'launchctl unload -w /path-to-plist' as root. I wait for launchctl to return and then wait for the daemon to terminate. Step #2: Delete the .plist at /Library/LaunchDaemons/QRecallScheduler501.plist. Step #3: Write a new .plist at /Library/LaunchDaemons/QRecallScheduler501.plist Step #4: Run 'launchctl load /path-to-plist' as root. Wait for launchctl to finish. Here's what happens: In step #1, launchctl returns with a status of 0. The daemon receives a SIGTERM and shuts down (2-3 seconds). IMMEDIATELY, launchd starts the new deamon. I can only assume because the location of the updated binary is the same as the old one that was just terminated. Steps #2 and #3 delete and rewrite the .plist. Step #4 runs 'launchctl load' which returns with a status of 0. What I get in the console log is 11/28/07 4:09:44 PM [0x0-0x1e01e].com.qrecall.client[145] launchctl: Error unloading: com.qrecall.scheduler 11/28/07 4:09:56 PM com.apple.launchd[62] (com.qrecall.scheduler.501) Ignored this key: UserName Contrary to the second error, the daemon is run with a UID of 501 (which is correct -- the daemon will terminate if it's started as root). The new daemon is then repeatedly restarted. (The daemon checks for a duplicate running instance of itself and terminates immediately if it's already running.) 11/28/07 4:09:57 PM com.apple.launchd[62] (com.qrecall.scheduler.501) Throttling respawn: Will start in 10 seconds 11/28/07 4:10:07 PM com.apple.launchd[62] (com.qrecall.scheduler.501) Throttling respawn: Will start in 10 seconds 11/28/07 4:10:17 PM com.apple.launchd[62] (com.qrecall.scheduler.501) Throttling respawn: Will start in 10 seconds 11/28/07 4:10:27 PM com.apple.launchd[62] (com.qrecall.scheduler.501) Throttling respawn: Will start in 10 seconds The really bad part is the instance of the daemon that is running does not seem to be running in the correct environment/namespace. When it launches a sub-process it attempts to connect with it using Mach ports; The connection fails. Restarting the OS doesn't fix the problem. I think the problem is that (in Leopard) there seems to be two instances of launchd running: One as root and one as user 501. But I'm getting very confused as to which one I should be trying to deal with. I changed the code to call launchctl while running as user 501. That sometimes works and sometimes doesn't. If I can get the daemon to stop and issue 'launchctl load /...' as user 501, the daemon starts working: specifically, it can communication with the sub-processes that it starts. Once started using 'launchctl' as user 501 it can be stopped again using launchctl as 501. But after a restart, it's running in the wrong namespace again and I have to perform a 'sudo launchctl unload' to get it to stop. So after an entire day, I'm really confused as to what launchctl commands I should be issuing to replace a running deamon, in what order, and using what UID. James -- James Bucanek

5 14