[launchd-dev] Path monitoring failed

[Dave Zarzycki]

Marit,

Launchd supposedly rechecks path monitoring checks every time the  
mount table is updated. Unfortunately, we don't log the transition  
from "it wasn't working" to "it now is being monitored" state. Is this  
genuinely not working for you? Or is the log message just concerning  
you?

davez


On Apr 24, 2008, at 7:31 AM, marit wrote:

>
> 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
>
>
>
>
>
> _______________________________________________
> launchd-dev mailing list
> launchd-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/launchd-dev