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

OnDemand USB Software
by Mike Fischer 11 Jul '08

11 Jul '08

Hi! I'm trying to evaluate if it is feasable to have an on-demand daemon depend on the presence of a certain usb device. I.e. I'd like the daemon to launch when the USB-device is plugged in. So far, looking at tn2083 and the man pages, I don't see any way to have a depency on USB or IOKit in general. Am I missing something here? If there is no direct support would it make sense to have a very small, lightweight daemon always running that registers for IOKit IOServiceAddMatchingNotification notifications and creates a semaphore file that can be used to trigger the launch of the real daemon for example? BTW: This would be mainly for Leopard, although Tiger would be interesting too. Thanks! Mike -- Mike Fischer Softwareentwicklung, EDV-Beratung Schulung, Vertrieb Web: <http://homepage.mac.com/mike_fischer/index.html> Note: I read this list in digest mode! Send me a private copy for faster responses.

3 2

launchd (257) not building
by Dave MacLachlan 06 May '08

06 May '08

> Hey Ryan... >> error: CoreFoundation/CFPriv.h: > No such file or directory I'm running into problems getting launchd > to compile as well, but at least for this part you can grab these > headers from > http://src.macosforge.org/Roots/9C31/CF.root.tar.gz Hope that helps > somewhat. I'm still looking for > bootfiles.h Further follow up, I haven't found bootfiles.h, but from what I can glean: #define kBootRootActiveKey "bootroot-active" #define SO_EXECPATH 0x1085 (could somebody please correct me if those values are wrong) but I can't find quarantine.h anywhere, and radar is currently down so I can't log a bug against it. I'm trying to build up liblaunch, so I can build up a debug version of libSystem so I can verify what appears to be a bug in libc_debug which is occurring when I run my app against the _debug frameworks that DTS is shipping. Talk about yak shaving. Cheers, Dave

5 8

Path monitoring failed
by marit 29 Apr '08

29 Apr '08

I have some launchd plists with WatchPaths that are watching directories on non-boot (but local internal SATA) drives. On 10.4 the watchpaths worked ok, but on 10.5.2, they are failing to load on boot. They do load and run correctly if I wait until after boot and load them manually with launchctl. Here is the section of syslog showing that "path monitoring failed" during startup: Apr 4 08:27:18 macgoesall com.apple.loginwindow[33]: System shutdown time has arrived Apr 4 08:27:44 localhost kernel[0]: npvhash=4095 Apr 4 08:27:42 localhost com.apple.launchctl.System[2]: /dev/disk0s3 on / (hfs, local, journaled) Apr 4 08:27:44 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/chum.plist Apr 4 08:27:44 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/ dashboardadvisoryd.plist Apr 4 08:27:44 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/ pilotfish.plist Apr 4 08:27:44 localhost com.apple.launchd[1] (com.apple.distccdConfigd): Unknown key: SHAuthorizationRight Apr 4 08:27:44 localhost com.apple.launchd[1] (org.cups.cupsd): Unknown key: SHAuthorizationRight Apr 4 08:27:44 localhost com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight Apr 4 08:27:44 localhost com.apple.launchd[1] (gov.nasa.gv_age_color_east): Path monitoring failed on "/Volumes/HD3/ color/east_out/hurricane2": No such file or directory Am I missing some launchd configuration that will fix this problem? This seems like something that could be solved if OnDemand could use the PathState key that KeepAlive has. Anyway, I finally modified my program to create files on the boot disk just for for launchd to watch and with that modification the path monitoring works fine; however I'd prefer not to have that added feature in my code since it just adds another directory that has to be created, passed into the program, cleaned, etc marit

2 2

launchd - how to specify daemon needs to wait for network to start?
by Jim Correia 22 Apr '08

22 Apr '08

I'm upgrading a server from 10.4 to 10.5 server. This server runs p4d (which really wants to listen/fork itself - there are restrictions on (x)inetd compatibility mode), and a handful of other jobs which should only be running after the p4d daemon has started. Currently, the launchd job is specified like this: <?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>KeepAlive</key> <dict> <key>NetworkState</key> <true/> </dict> <key>Label</key> <string>com.perforce.p4d</string> <key>ProgramArguments</key> <array> <string>/usr/local/bin/p4d</string> ... </array> </dict> </plist> It appears that p4d is first launched before the network interface is up. (The error information in the log isn't extremely verbose. It looks like it is trying to bind to the address in the license file, and this fails.) After one or more respawn attempts, the server comes. What is the correct way to spec the job? Jim

3 3

Launching tunnel driver with launchd?
by Andre-John Mas 18 Apr '08

18 Apr '08

Hi, I have a daemon that depends on a tunnel driver to be loaded, for it to be able to function. Both are currently using StartupItems, so I would like to migrate them to use launchd. The daemon is aiccu, a 6to4 tunnel, and the driver is tun/tap. What I would like to know is what is the right way to loading the tun/ tap driver with launchd, if launchd is the right mechanism for this? For the aiccu side, it would appear that the SampleD example: http://developer.apple.com/samplecode/SampleD/index.html would be my point of reference. Any help would be appreciated. Andre

1 0

launchd support ranges for StartCalendarInterval?
by Richard Glaser 10 Apr '08

10 Apr '08

Hello Dave: Emailed this answer in the past and I was wondering if he or someone else would be willing to email out a example for a range of hours by having StartCalendarInterval be an array of dictionaries instead of just a dictionary... Would it be something like this.? <key>StartCalendarInterval</key> <array> <key>Hour</key> <integer>4</integer> <key>Minute</key> <integer>0</integer> <key>Weekday</key> <integer>0</integer> </array> <array> <key>Hour</key> <integer>5</integer> <key>Minute</key> <integer>0</integer> <key>Weekday</key> <integer>0</integer> </array> For every range of hours? > Yes, you can do this. Have StartCalendarInterval be an array of > dictionaries instead of just a dictionary within the configuration > file. Having said that, it would be nice if launchd natively supported > some of the common calendar expressions such as > {first,second,third,forth,last,second-to-last} > {mon,tue,wed,thr,fri,sat,sun}. Doing so would save people the trouble > of figuring out the ranges. > > Feel free to file an enhancement request, > > davez > > P.S. -- I've occasionally wanted, just for giggles, to have launchd to > support other time intervals such as "only during leap years" or the > ability to schedule jobs based on the phase of the moon, or the > solstices/equinoxes. I've even considered adding planetary alignment > to the schema. :-P Thanks: Richard Glaser University of Utah - Student Computing Labs richard(a)scl.utah.edu 801-585-8016

1 0

Re: [launchd-dev] How to on demand launch for configurable port number?
by Mike Fischer 03 Apr '08

03 Apr '08

Am 03.04.2008 um 08:30 schrieb Quinn <eskimo1(a)apple.com>: > > At 10:20 +0100 2/4/08, Quinn wrote: >> At 17:05 +0200 1/4/08, Mike Fischer wrote: >>> So "unload" makes launchd completely forget about a service while >>> "load" does the reverse? >> >> Right. > > OK, that's was a little more succinct that I originally intended. :-) Would have helped on it's own though. I was just making sure I understood because some experiments I did with a custom Launch Agent to create a system profile report once per day (for having it handy when filing bug reports) seemed to make it necessary to logout/login to make it work. I tried unload/load (I think) without success but I didn't document my exact steps to get it to work. I'll just mark this off as experimenting with too many unknown variables and too little knowledge. The Launch Agent now works btw. > Here's some more background: > > This one super-confusing part of launchd if you're coming to it from > scratch. The lifecycle of a job is: > > load -> start -> stop -> [...] -> unload > > The load can be done implicitly (typically at the start of a session, > for example, at startup time launchd loads all of the enabled jobs in > /System/Library/LaunchDaemons) or explicitly (via "launchctl load"). > Unloads, per se, only happen explicitly (via "launchctl unload"), but > jobs are effectively unloaded if the session that they're loaded into > dies (keep in mind that launchd's global session never dies). > > Similarly, the start can be done implicitly (via the RunAtLoad > property, or by meeting one of your the launch-on-demand criteria, or > by the KeepAlive property) or explicitly (via "launchctl start"). > And a stop happens when the job quits or, explicitly, via "launchctl > stop". Thanks for the very clear explanation. Mike -- Mike Fischer Softwareentwicklung, EDV-Beratung Schulung, Vertrieb Note: I read this list in digest mode! Send me a private copy for faster responses.

1 0

launch Agent
by Pradip Patel 03 Apr '08

03 Apr '08

Hi Is LaunchAgent work on non-admin mode ? which permissing i have to set for it on 10.5 ? p2 -- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________

1 0

Re: [launchd-dev] StartupItems
by Pradip Patel 03 Apr '08

03 Apr '08

first Thanks My application is console base...so how is going to connect windowserver ? May be i am using CGDisplayCurrentMode API of Quartz ? How can I get main screen resolution with such api which is not interact with window server ? can you please tell me such API ? if i made my application trusted then above quartz API get success ? p2 ----- Original Message ----- From: "Quinn" <eskimo1(a)apple.com> To: <launchd-dev(a)lists.macosforge.org> Sent: Wednesday, April 02, 2008 4:07 PM Subject: Re: [launchd-dev] StartupItems > At 15:40 +0530 2/4/08, Pradip Patel wrote: >>do I have to sign the code ? > > No. To quote from the technote: > > If, in Mac OS X 10.5 and later, you see a message like > that shown in Listing 9 you might mistakenly think that > the solution is to get the system to 'trust' your > application, perhaps via code signing. > > However, this isn't the case. This message is really > telling you is that you're trying to connect to the > window server from the wrong context. You see this > message if you try to connect to the global window > server service from outside of the pre-login context > before the user has logged in; typically this means that > you're trying to use the window server from a daemon. > >>or change the code ? > > Yes. Again, to quote from the technote: > > You should not attempt to fix this by convincing the > window server to trust your program; doing so will just > cause other problems further down the road. For example, > if you do successfully connect to the window server from > your daemon, you still have to deal with window server > lifecycle issues described previously. > > Instead, you should fix this problem by changing your > code to run in the correct context. If you need to > connect to the window server in a pre-login context, > create a pre-login launchd agent. For an example of > this, see Sample Code Project 'PreLoginAgents'. > > S+E > -- > Quinn "The Eskimo!" <http://www.apple.com/developer/> > Apple Developer Relations, Developer Technical Support, Core OS/Hardware > _______________________________________________ > launchd-dev mailing list > launchd-dev(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/launchd-dev > > - This message has been scanned for viruses, spam and dangerous content > and is believed to be clean. > -- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________

1 0

StartupItems
by Pradip Patel 02 Apr '08

02 Apr '08

Hi Is there any difference in /Library/StartupItems in MacOS 10.4 vs 10.5 ? p2 -- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________

3 7