November 2008 - launchd-dev - lists.macosforge.org

SampleD failure with dynamic SockServiceName
by David Anderson 13 Aug '09

13 Aug '09

My intention is have launchd start a daemon on a dynamic port, publish the port number via bonjour, and then connect to this port after determining the port number using CFNetService (Bonjour). Starting from SampleD (and using the included client.pl), I can advertise the service on a hard-coded port via bonjour, lookup the port number using Bonjour Browser, modify client.pl to use this port, and connect using client.pl. The SampleD binary starts correctly in an OnDemand fashion correctly. If I change <key>SockServiceName</key> <string>12345</string> to <key>SockServiceName</key> <string>0</string> then lookup the dynamic port number using Bonjour Browser and configure client.pl to use this port, client.pl will NOT connect to this port and outputs this error: connect: Connection refused at ./client.pl line 77. With a dynamic port, I am unable to connect to this port using a modified client.pl. I can find no evidence that the SampleD binary is starting in an OnDemand fashion. Adding <key>OnDemand</key> <false/> has no effect. Is there anything different about the default configuration of a dynamic port vs a hard-coded port that would impeded the ability to connect to the dynamically assigned port? Thanks, Dave

3 2

LaunchDaemon unable to launch and causing messages in log
by pavan kumar 09 Dec '08

09 Dec '08

Hi, When I am trying to Launch my launchdaemon I am getting an error "Bug: launchd_core_logic.c:3011 (23585):0: initgroups(loginname, desired_gid) != -1" and my daemon is not getting launched. Please let me know what is the reason for this error. Thanks Pavan

3 7

fork & exit in Shell Script
by Charles Darwin 19 Nov '08

19 Nov '08

Hi all, I have a shell script that runs RunAtLoad. Here is the script: ######## /bin/test -f /Volumes/tutorials || /bin/mkdir -p /Volumes/tutorials && /sbin/mount_afp afp://username:password@url/tutorials/ /Volumes/ tutorials/ /bin/test -f /Volumes/homes || /bin/mkdir -p /Volumes/homes && /sbin/ mount_afp afp://username:password@url/homes/ /Volumes/homes/ ######## and here is the plist: ------------------ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http:// www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>label</string> <key>ProgramArguments</key> <array> <string>path/to/script</string> </array> <key>StartCalendarInterval</key> <dict> <key>RunAtLoad</key> <true/> </dict> </dict> </plist> ------------------ It takes almost a minute after my users login to see the afp sharepoint mounted. Here is the log from syslog: ------------------ Oct 29 11:49:31 … loginwindow[240] <Error>: Login Window Started Security Agent Oct 29 11:49:31 … SecurityAgent[248] <Error>: Showing Login Window Oct 29 11:51:00 … launchd[204] <Warning>: <label>: exited with exit code: 58 Oct 29 11:51:00 … launchd[204] <Warning>: <label>: 9 more failures without living at least 60 seconds will cause job removal Oct 29 11:52:00 … launchd[204] <Warning>: <label>: exited with exit code: 58 Oct 29 11:52:00 … launchd[204] <Warning>: <label>: 8 more failures without living at least 60 seconds will cause job removal Oct 29 11:53:00 … launchd[204] <Warning>: <label>: exited with exit code: 58 Oct 29 11:53:00 … launchd[204] <Warning>: <label>: 7 more failures without living at least 60 seconds will cause job removal Oct 29 11:54:00 … launchd[204] <Warning>: <label>: exited with exit code: 58 Oct 29 11:54:00 … launchd[204] <Warning>: <label>: 6 more failures without living at least 60 seconds will cause job removal Oct 29 11:55:00 … launchd[204] <Warning>: <label>: exited with exit code: 58 Oct 29 11:55:00 … launchd[204] <Warning>: <label>: 5 more failures without living at least 60 seconds will cause job removal Oct 29 11:56:00 … launchd[204] <Warning>: <label>: exited with exit code: 58 Oct 29 11:56:00 … launchd[204] <Warning>: <label>: 4 more failures without living at least 60 seconds will cause job removal Oct 29 11:57:00 … launchd[204] <Warning>: <label>: exited with exit code: 58 Oct 29 11:57:00 … launchd[204] <Warning>: <label>: 3 more failures without living at least 60 seconds will cause job removal Oct 29 11:58:00 … launchd[204] <Warning>: <label>: exited with exit code: 58 Oct 29 11:58:00 … launchd[204] <Warning>: <label>: 2 more failures without living at least 60 seconds will cause job removal Oct 29 11:59:00 … launchd[204] <Warning>: <label>: exited with exit code: 58 Oct 29 11:59:00 … launchd[204] <Warning>: <label>: 1 more failure without living at least 60 seconds will cause job removal Oct 29 12:00:00 … launchd[204] <Warning>: <label>: exited with exit code: 58 Oct 29 12:00:00 … launchd[204] <Warning>: <label>: too many failures in succession ------------------ Does this have anything to do with "your daemon must not daemonize itself (fork and exit)"? (whatever that means) Any idea how I can fix it? Thanks, Charles

5 20

Daemon & Network Availability?
by Karl Moskowski 14 Nov '08

14 Nov '08

Hello, all! I'm working on a project comprised of a launchd daemon and a GUI client app. I used the BetterAuthorizationSample project as a template for installing and starting up the daemon the first time. In the daemon's start-up code, it connects to a remote server. It all works fine on installation. However, when I reboot my computer, the daemon starts up, but the network isn't available yet, and the connection fails. I tried using SystemConfiguration notifications to receive changes to the network state, but that doesn't work - the computer has an IP address at that point, but the remote server is still not reachable. I also tried setting the KeepAlive option in the daemon's plist to NetworkState = true. However, that doesn't seem to work either - it just starts as KeepAlive = true. Is there some other way to indicate a dependency on the network? Do I need a delay at start up to wait for a connection? For better or worse, I used a named DO connection to handle IAC between the daemon & GUI. Could this be part of the problem (the caveats in TN2083 lead me to believe it's just inadvisable but not wrong outright)? Also, is launchd checkin, etc., required? I did have it in main(), but it kept failing, even though I had ServiceIPC = true. In case it helps, the current daemon plist is below. Thanks. ---- Karl Moskowski <kolpanic(a)voodooergonomics.com> Voodoo Ergonomics Inc. <http://voodooergonomics.com/> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd "> <plist version="1.0"> <dict> <key>KeepAlive</key> <dict> <key>NetworkState</key> <true/> </dict> <key>Label</key> <string>com.company.myd</string> <key>ProgramArguments</key> <array> <string>/Library/PrivilegedHelperTools/com.company.myd</string> </array> </dict> </plist>

3 6

Re: [launchd-dev] Daemon & Network Availability?
by Karl Moskowski 10 Nov '08

10 Nov '08

So, I've been doing a bit of research, and I've noticed a couple of effects: - for the launchd checkin process to succeed, the daemon's plist needs a Sockets section and ServiceIPC=true - at boot time, to have the daemon launch only when the network is available, set RunAtLoad=false and KeepAlive={NetworkState=true} These two are independent; if I omit the Sockets & ServiceIPC and checkin in main(), then reboot with no network, the daemon starts after I connect the ethernet cable. There are few complications: - launchd loads the daemon as soon as the network interface is available, before it has a valid IP address. - launchd loads the daemon at boot if any network interfaces are connected (e.g., Parallels ports) - launchd doesn't unload the daemon automatically if the network goes down To workaround the first two, I guess I could put a reachability test in the initialization code of main() and exit if I can't get to the server, allowing launchd to reload the daemon automatically. For the last, I can also exit if the connection dies and let launchd control resurrection. What do you think? ---- Karl Moskowski <kolpanic(a)voodooergonomics.com> Voodoo Ergonomics Inc. <http://voodooergonomics.com/>

1 0

Re: [launchd-dev] Diagnosing launchd daemon failure to launch
by Iain Delaney 10 Nov '08

10 Nov '08

Ahh, that was the problem. So the real issue is that my daemon is loading, but not responding to my client app. I'm trying to use Distributed Objects on top of UNIX Domain sockets. The directory for the socket is /var/tmp, and the client and server can communicate if I run both programs inside XCode. However, when I move the daemon program to /Library/PrivilegedHelperTools and copy to plist into /Library/LaunchDaemons everything stops working. The client seems to be hanging while trying to connect to the socket. Any ideas what I'm doing wrong? Thanks, Iain At 10:46 -0500 5/11/08, Iain Delaney wrote: >Then I reboot, and run 'launchctl list' in the terminal. Did you use "sudo launchctl list", or just "launchctl list"? The latter will show you the list of jobs for login session launchd, not for the global launchd. S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware

5 9

Diagnosing launchd daemon failure to launch
by Iain Delaney 05 Nov '08

05 Nov '08

Hello all, I was wondering if you could help me with a launchd issue I'm having problems with. I've built my daemon and installed it in /Library/ PrivilegedHelperTools. I've made a launchd plist for it, and put the plist in /Library/LaunchDaemons. Then I reboot, and run 'launchctl list' in the terminal. I can't see my daemon; it appears that it didn't get loaded. If I then run 'launchctl load /Library/LaunchDaemons' and then run the 'list' again, I can see the daemon with a pid. This tells me that the plist and the file locations are okay, I think. I don't see anything in the console logs (I previously had problems with the ownership of the plist, but that seems to be fixed). Would anyone have any idea what's going wrong, or how I can diagnose the problem? Thanks in advance, Iain Delaney

2 1

RunAtUnLoad
by Charles Darwin 03 Nov '08

03 Nov '08

Hi all, Is there any key that tells launchd to run something when user logs out? Thanks, Charles

1 0