Hi,
Bit of a weird one with launchd on a 10.4.10 Intel Server. I’ve got a script that runs and sends notification emails when users drop files in their drop boxes. It all works perfectly fine, the launchd.plist files all use watchpaths and when a file is added the script is fired and emails get sent out OK. The problem is that there are quite a few of these folders to watch (about 60 or so) and while the whole thing seems to work, launchd “loses” some of the launchd.plists that have been loaded in.
So for instance I do a launchctl load on all the 60 plist files, and when I do a launchctl list they all appear to be there. I test everything and emails are being sent without a problem. Some time later (it seems to vary how long) the users get in touch saying that the notifications have stopped working. I check with launchctl list and there are only 40 or so items there (it tends to drop a chunk of them in alphabetical order, so today all the plists that start with com.company.a…. to com.company.f… have disappeared, whereas com.company.f… to com.company.w…. are still there).
Is there a fixed limit to the number of items that can be loaded into launchd? I can’t seem to find a mention of this anyway, but I can’t find any other reason why launchd would lose the items.
Thanks for any help!
Skaff.
.
.
Comments are closed