September 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

[Un]loading user agents on [Un]install
by Tim Schooley 30 Sep '08

30 Sep '08

Hi all, So I think this is probably quite a "sane" task to have to perform: - Upon installing a product, detect which users are logged in, and load the installed LaunchAgent script for each user. - Upon uninstalling the product, detect which users are logged in, and unload the LaunchAgent script for each user. These tasks would be performed preupgrade, postinstall, etc... I wrote the following script to perform this task: ---- for user in `/usr/bin/users` do echo "Loading agent for user $user..." /usr/bin/su -l $user -c "/bin/launchctl load -SAqua /Library/LaunchAgents/com.mycompany.myproduct.plist" EXIT_STATUS=$? if [ $EXIT_STATUS != 0 ] then echo "failed (non-fatal, status $EXIT_STATUS)." else echo "Done!" fi done ---- And similarly for unloading. The script works for the user that launched the installer. But if for example another user is logged in using Fast-User Switching, the following error is printed in the installer log when preupgrade attempts to unload the script: preupgrade[pid]: launchctl: Error unloading: com.mycompany.myproduct.plist Also, on post[upgrade/install], the following error is printed when attempting to load the script for other users: postupgrade[pid]: launch_msg(): socket is not connected I've searched around for answers to these issues, but had no luck. I was hoping someone here might be able to point me in the right direction? Many thanks for any help! Kind regards, Tim

2 2

Building launchd(8) from SVN on 10.5.5
by R. Tyler Ballance 28 Sep '08

28 Sep '08

Trying to get a working build from Subversion running on my 10.5.5 Intel machine (Core Duo), is there a version of Xcode 3 I'll be needing to build launchd(8) on Mac OS X nowadays? make all-am gcc -DHAVE_CONFIG_H -I. -I/Volumes/Juicebox/Software/launchd/launchd/src -fvisibility=hidden -freorder-blocks -fdiagnostics-show-option -isysroot / -F//System/Library/PrivateFrameworks -Dmig_external=__private_extern__ -D_DARWIN_USE_64_BIT_INODE=1 -Wall -Wextra -Waggregate-return -Wfloat-equal -Wshadow -Wpacked -Wmissing-prototypes -Wmissing-declarations -Werror -Wstrict-overflow=4 -isystem //System/Library/Frameworks/System.framework/PrivateHeaders -arch ppc -arch ppc64 -arch i386 -arch x86_64 -g -Os -pipe -c -o launchctl-launchctl.o `test -f 'launchctl.c' || echo '/Volumes/Juicebox/Software/launchd/launchd/src/'`launchctl.c cc1: error: unrecognized command line option "-Wstrict-overflow=4" cc1: error: unrecognized command line option "-fdiagnostics-show-option" cc1: error: unrecognized command line option "-Wstrict-overflow=4" cc1: error: unrecognized command line option "-fdiagnostics-show-option" cc1: error: unrecognized command line option "-Wstrict-overflow=4" cc1: error: unrecognized command line option "-fdiagnostics-show-option" cc1: error: unrecognized command line option "-Wstrict-overflow=4" cc1: error: unrecognized command line option "-fdiagnostics-show-option" lipo: can't open input file: /private/tmp/ccSExAiU.out (No such file or directory) make[3]: *** [launchctl-launchctl.o] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [build] Error 2 R-Tyler-Ballances-Computer% uname -a Darwin R-Tyler-Ballances-Computer.local 9.5.0 Darwin Kernel Version 9.5.0: Wed Sep 3 11:29:43 PDT 2008; root:xnu-1228.7.58~1/RELEASE_I386 i386 R-Tyler-Ballances-Computer% gcc --version i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465) Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. R-Tyler-Ballances-Computer%

2 1

launchd on freebsd
by Tsvetomir Dimitrov 28 Sep '08

28 Sep '08

Hello, There was a Google Summer of code project about porting launchd on FreeBSD. Is this project still active? Have you got any information about it or any other similar? I will be very happy to see launchd working on FreeBSD. Unfortunately I am still a beginner programmer, but I'll do my best to contribute in my free time. Thank you in advance! Best regards, Tsvetomir

4 4

Re: [launchd-dev] launchd-dev Digest, Vol 15, Issue 10
by Ryan McGann 25 Sep '08

25 Sep '08

On Sep 25, 2008, at 7:00 AM, launchd-dev-request(a)lists.macosforge.org wrote: >> I'm wondering about the relationship between NetworkState and the >> networking >> stack. I haven't found a reference about the KeepAlive/NetworkState >> value >> and the relative order in launching jobs with it versus the loading >> of the >> network stack. >> >> When NetworkState is true, will that result in a job that starts >> before, >> during, or after the loading of the network stack? Is that order >> guaranteed? > > Ultimately, I'd like to launch something _before_ the network stack > has > loaded, but only really need load it when -- and as long as -- the > network > stack will be active. Jeremy, launchd and the mechanisms it uses to receive notification that the network stack is up are asynchronous and callback-oriented, which means there is no guarantee of ordering. When launchd is notified an IP address has been assigned to an interface, the network stack is already "up", so there's no way to use NetworkState to be called before interfaces have had any addresses assigned to them. Even so, with all the launchd plists installed by Leopard, it's very likely that by the time launchd gets around to loading your process, the network is already up and sending out mDNS packets (on a Mac Pro that uses a static IP address with wired Ethernet, an interface coming online happens *very* early and *very* quickly during system startup) . On my latest-gen iMac, we're process ID 50 and the network is very much alive when we load. However you could set the RunAtLoad key, which will start your daemon as soon as the machine starts up. The network may already be up at that point so you should use SystemConfiguration/ SCNetworkCheckReachability/ifconfig/etc to check if the network is already up, and do your work appropriately. Otherwise it could exit, and hope the network doesn't come online while you are exiting (as I think there's a race condition in there that we've experienced). When the network goes offline, launchd should then ask you to exit, and then relaunch you as necessary. If you absolutely must be guaranteed that your daemon is called before any addresses are assigned to the machine, you cannot use launchd. Again, this is all from my experience—somebody else might prove me wrong. Ryan

1 0

NetworkState and order
by Jeremy Reichman 25 Sep '08

25 Sep '08

I'm wondering about the relationship between NetworkState and the networking stack. I haven't found a reference about the KeepAlive/NetworkState value and the relative order in launching jobs with it versus the loading of the network stack. When NetworkState is true, will that result in a job that starts before, during, or after the loading of the network stack? Is that order guaranteed? Thanks! -- Jeremy

1 1

Re: [launchd-dev] launchd on freebsd
by Tsvetomir Dimitrov 25 Sep '08

25 Sep '08

Please excuse my last reply. I was a bit sleepy and missed the expat part. We can use libxml2 (http://xmlsoft.org/) It can parse a XML file to tree and some other functionality which we may or may not use. ezXML (http://ezxml.sourceforge.net/) is also a solution. It's smaller and simpler than libxml. I think libxml2 is better choice. I'm not sure however if ezXML won't perform better because its smaller. What do you think about this? Also do you know if the lib should have BSD license in order to be included in the FreeBSD's base? Cheers, Tsvetomir ----- Original Message ---- From: R. Tyler Ballance <tyler(a)monkeypox.org> To: Tsvetomir Dimitrov <tsurko(a)yahoo.com> Cc: Dave Zarzycki <zarzycki(a)apple.com>; Launchd-dev <launchd-dev(a)lists.macosforge.org> Sent: Monday, 22 September, 2008 15:30:50 Subject: Re: [launchd-dev] launchd on freebsd On Mon, 2008-09-22 at 05:16 -0700, Tsvetomir Dimitrov wrote: > Excellent news! Can I help with anything? As I've already said I'm a > beginner. Programming is my hobby and I've just started to work as > professional C programmer. So if you think I can be useful in some way > do not hesitate to write me! Well, you don't necessarily have to go along with the direction I'm taking, but if you're on board, I could certainly use help and I think it would generally help the project if we started adding test coverage to launchd(8) by way of CUnit (http://cunit.sourceforge.net/) I'm a big fan of test-driven porting projects ;) One thing I actually loathe is working with expat, and we will likely need a plist XML file parser. I'm not entirely certain on the FreeBSD project's views on the APSL, but I think one way or another CF-lite is out of the picture (especially if we aim to push this into FreeBSD base). If you're up for it, I think that'd be a great place to start. If you'd like I can push my Git repository to a public web server where we can both collaborate on the development of test cases. What I've done thus far is really not much more than reacquainting myself with launchd(8)'s code, it feels like home, even after all these years :) Cheers, -R. Tyler Ballance > Best regards, > Tsvetomir > > > ----- Original Message ---- > From: R. Tyler Ballance <tyler(a)monkeypox.org> > To: Dave Zarzycki <zarzycki(a)apple.com> > Cc: Tsvetomir Dimitrov <tsurko(a)yahoo.com>; Damien Sorresso > <dsorresso(a)apple.com>; Launchd-dev <launchd-dev(a)lists.macosforge.org> > Sent: Monday, 22 September, 2008 7:39:59 > Subject: Re: [launchd-dev] launchd on freebsd > > On Sun, 2008-09-21 at 18:03 -0700, Dave Zarzycki wrote: > > Tsvetomir, > > > > > > Funny that you should ask. R. Tyler Ballance, the author of the > Googleted to > > Summer of Code project, just emailed me about potentially reviving > the > > port. Hopefully our new launchd maintainer, Damien, can help you > both > > coordinate any porting activity. > > (resending since the mailing list ate my first version) > > I'd like to point out that all work on the previous port of mine is > likely a total wash as it was before zarzycki@ made a large chunk of > changes for the version of launchd(8) for Leopard. > > As it stands now I'm working in a Git repository sitting on my FreeBSD > RELENG_6 machine simply working on getting components compiled or > #ifdef'd out such that they will compile on non-Apple systems. > > The approach I intend on taking this time around is to build some > CUnit > tests around some of the base levels of functionality before I move > onto > the more complicated mach-port-based process management and IPC > mechanisms. I also do not intend on building in any implicit > FreeBSD-isms, as I'd like to take launchd(8) over to my openSUSE > workstations in the future as well ;) > > > Consider any code you find of mine in the FreeBSD perforce repository > as > antique and testament to how much of a n00b I used to be ;) > > > > I'll keep the thread updated on any progress :) > > > Cheers, > -R. Tyler Ballance > > > > Best of luck to you all, > > > > > > davez > > > > > > > > > > > > > > > > On Sep 21, 2008, at 3:16 PM, Kevin Van Vechten wrote: > > > > > I'm not aware of any current activity surrounding that effort, but > > > it's something we'd like to see. Have you checked the list > archives > > > to see where things left off? > > > > > > > > > On Sep 20, 2008, at 3:28 PM, Tsvetomir Dimitrov <tsurko(a)yahoo.com> > > > wrote: > > > > > > > > > > > > > Hello, > > > > There was a Google Summer of code project about porting launchd > on > > > > FreeBSD. Is this project still active? Have you got any > > > > information about it or any other similar? I will be very happy > to > > > > see launchd working on FreeBSD. Unfortunately I am still a > > > > beginner programmer, but I'll do my best to contribute in my > free > > > > time. > > > > Thank you in advance! > > > > > > > > Best regards, > > > > Tsvetomir > > > > > > > > > > > > > > > > _______________________________________________ > > > > launchd-dev mailing list > > > > launchd-dev(a)lists.macosforge.org > > > > http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev > > > > > > > _______________________________________________ > > > launchd-dev mailing list > > > launchd-dev(a)lists.macosforge.org > > > http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev > > > > > > _______________________________________________ > launchd-dev mailing list > launchd-dev(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

2 1

Re: [launchd-dev] launchd on freebsd
by Tsvetomir Dimitrov 23 Sep '08

23 Sep '08

I think if we work together we'll have better results. You are more experienced, so lead the way:). About the XML parser maybe we can use expat. It should do the job. What do you think about it? Cheers, Tsvetomir ----- Original Message ---- From: R. Tyler Ballance <tyler(a)monkeypox.org> To: Tsvetomir Dimitrov <tsurko(a)yahoo.com> Cc: Dave Zarzycki <zarzycki(a)apple.com>; Launchd-dev <launchd-dev(a)lists.macosforge.org> Sent: Monday, 22 September, 2008 15:30:50 Subject: Re: [launchd-dev] launchd on freebsd On Mon, 2008-09-22 at 05:16 -0700, Tsvetomir Dimitrov wrote: > Excellent news! Can I help with anything? As I've already said I'm a > beginner. Programming is my hobby and I've just started to work as > professional C programmer. So if you think I can be useful in some way > do not hesitate to write me! Well, you don't necessarily have to go along with the direction I'm taking, but if you're on board, I could certainly use help and I think it would generally help the project if we started adding test coverage to launchd(8) by way of CUnit (http://cunit.sourceforge.net/) I'm a big fan of test-driven porting projects ;) One thing I actually loathe is working with expat, and we will likely need a plist XML file parser. I'm not entirely certain on the FreeBSD project's views on the APSL, but I think one way or another CF-lite is out of the picture (especially if we aim to push this into FreeBSD base). If you're up for it, I think that'd be a great place to start. If you'd like I can push my Git repository to a public web server where we can both collaborate on the development of test cases. What I've done thus far is really not much more than reacquainting myself with launchd(8)'s code, it feels like home, even after all these years :) Cheers, -R. Tyler Ballance > Best regards, > Tsvetomir > > > ----- Original Message ---- > From: R. Tyler Ballance <tyler(a)monkeypox.org> > To: Dave Zarzycki <zarzycki(a)apple.com> > Cc: Tsvetomir Dimitrov <tsurko(a)yahoo.com>; Damien Sorresso > <dsorresso(a)apple.com>; Launchd-dev <launchd-dev(a)lists.macosforge.org> > Sent: Monday, 22 September, 2008 7:39:59 > Subject: Re: [launchd-dev] launchd on freebsd > > On Sun, 2008-09-21 at 18:03 -0700, Dave Zarzycki wrote: > > Tsvetomir, > > > > > > Funny that you should ask. R. Tyler Ballance, the author of the > Googleted to > > Summer of Code project, just emailed me about potentially reviving > the > > port. Hopefully our new launchd maintainer, Damien, can help you > both > > coordinate any porting activity. > > (resending since the mailing list ate my first version) > > I'd like to point out that all work on the previous port of mine is > likely a total wash as it was before zarzycki@ made a large chunk of > changes for the version of launchd(8) for Leopard. > > As it stands now I'm working in a Git repository sitting on my FreeBSD > RELENG_6 machine simply working on getting components compiled or > #ifdef'd out such that they will compile on non-Apple systems. > > The approach I intend on taking this time around is to build some > CUnit > tests around some of the base levels of functionality before I move > onto > the more complicated mach-port-based process management and IPC > mechanisms. I also do not intend on building in any implicit > FreeBSD-isms, as I'd like to take launchd(8) over to my openSUSE > workstations in the future as well ;) > > > Consider any code you find of mine in the FreeBSD perforce repository > as > antique and testament to how much of a n00b I used to be ;) > > > > I'll keep the thread updated on any progress :) > > > Cheers, > -R. Tyler Ballance > > > > Best of luck to you all, > > > > > > davez > > > > > > > > > > > > > > > > On Sep 21, 2008, at 3:16 PM, Kevin Van Vechten wrote: > > > > > I'm not aware of any current activity surrounding that effort, but > > > it's something we'd like to see. Have you checked the list > archives > > > to see where things left off? > > > > > > > > > On Sep 20, 2008, at 3:28 PM, Tsvetomir Dimitrov <tsurko(a)yahoo.com> > > > wrote: > > > > > > > > > > > > > Hello, > > > > There was a Google Summer of code project about porting launchd > on > > > > FreeBSD. Is this project still active? Have you got any > > > > information about it or any other similar? I will be very happy > to > > > > see launchd working on FreeBSD. Unfortunately I am still a > > > > beginner programmer, but I'll do my best to contribute in my > free > > > > time. > > > > Thank you in advance! > > > > > > > > Best regards, > > > > Tsvetomir > > > > > > > > > > > > > > > > _______________________________________________ > > > > launchd-dev mailing list > > > > launchd-dev(a)lists.macosforge.org > > > > http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev > > > > > > > _______________________________________________ > > > launchd-dev mailing list > > > launchd-dev(a)lists.macosforge.org > > > http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev > > > > > > _______________________________________________ > launchd-dev mailing list > launchd-dev(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

1 0

LaunchAgents & Parental Controls
by Peter Alshuth 23 Sep '08

23 Sep '08

Hi all, I discovered an issue that my agent (a background Cocoa app) is not getting launched (from /Library/LaunchAgents/) when parental controls (Leopard) are active for a specific user account. Is this limited only to carbon/cocoa apps that they have to be in the list of allowed apps or can I set some kind of flags in order to have launchd launched my agent successfully? Unfortunately, I don't have the app stored inside the user's folder or the application directory, so the parental control panel doesn't list it automatically to offer it. Any kind of non-standard solution available, like editing a settings files (which one?) by a script while my installer creating all the daemon and agent related files? I really don't want to tell my end users to go into the parental control panel for each person's account and adding my agent app. I thought that the plist file permission for the launch agents has to be 'root/whell -rw-r--r--' permission set in order to get handled correctly. That would mean that no non-admin users can change its description in order to bypass e.g. the parental control settings. It makes no sense for me why a launch agent app needs to be on the parental control list in this case. Thanks for any help, Peter

1 0