On Thu, 2008-06-12 at 18:46 +0300, Andrei Cristian Niculae wrote: > > I've just tried passing --daemon switch and commented the RunAsDaemon > from the cfg, and I get the same result. > But why does sipxpbx status report mrtg as OK, even if sipXsupervisor > sends mail that it's not O.K., and is actually FAILED? > > If I write the pid of the first instance of the mrtg in the pid file, > than I get > Checking sipx-mrtg: [FAILED] > which I suppose it's normal, since the pid will not exist eventually. > > Does sipXsupervisor have a problem with programs that execs themselves > and than quit, to run as daemon? > I see that sipxcallresolver has a parameter --daemon when invoked so > I'm guessing that NO. > > Anyone can explain what's happening?
I can't comment on how mrtg should be set up to make it work, but the requirement is pretty simple - the pid file needs to exist, and contain just the integer pid of the managed process. -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
