Hi Rob, I think your right about the respawning. Makes sense, that the runclient.sh just stops after it calls up the other programs.
I do know that runclient.sh called by itself works. I'll try and spend more time on a better formed plist.
On 28/05/09 4:14 PM, "Rob McBroom" <mailinglist0 at skurfer.com> wrote:
On 2009-May-28, at 1:24 PM, William Ottley wrote:
<key>Label</key> <string>xymon</string>The label should probably be something like "dk.hswn.xymon" to guarantee uniqueness. (That's the convention used by all the existing plists.)
<key>Program</key> <string>/Users/xymon/client/runclient.sh</string>I don't know for certain, but I think launchd should be replacing the runclient.sh script, not calling on it. For instance, the script is designed to start up the Xymon client and then exit, whereas launchd expects the thing it started to keep running. You may have to dig into the script to figure out what it does on a Mac and then tell launchd to do that. (From just a quick scan, it looks like it needs to call
hobbitlaunchwith the appropriate options for your system.)A list of what launchd expects from the program it calls can be found in the man page for
launchd.plist. I don't know enough about hobbitlaunch to tell you if it meets those requirements, but I'm pretty sure the shell script does not based on the fact that it exits.This might have nothing to do with the error Xymon throws, but it would at least explain why launchd keeps restarting the script.
d.plist.5.html
-- This message has been scanned for dangerous content by MailScanner, and is believed to be clean.