The "common" error (at least for me) is that I install the code tree
as myself yet I run the keepalive_monitors as a fictious user (for
examnple, "nocol") -- and I also test "new" stuff as myself (which
causes the *.pid file to get created as me).
I'm not sure if this is still a bug or not, but does noclogd remove
the PID file if it exits successfully?
Russell
On Fri, Apr 21, 2000 at 09:22:01AM -0400, Vikas Aggarwal wrote:
> Either the noclogd was started as a different user or the $nocolroot/run
> directory is not writable by the process (or the previous noclogd.pid file
> has a different user's permissions).
>
> -vikas
>
> Ron Parker wrote:
> >
> > Now I'm starting to get this hourly. What's the deal, and how to I
> > correct it? Also, why did it just start happening after? The only
> > other new element is that one of the machines being portmonitored went
> > down earlier today, and that's when this started. I restarted the
> > monitored and monitoring machines, and thats when this started. Any
> > suggestions?
> >
--
Russell M. Van Tassell
russell@loosenut.com
Sorry, no fortune at this time.
|