[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Behaviour change request.

From: Eetu Rantanen
Subject: Re: Behaviour change request.
Date: Tue, 1 Oct 2002 12:28:50 +0300 (EEST)

> I'm not sure why you was able to actually kill this Java process.
> Maybe it wasn't started from within monit in the first place and it
> was a light-weight process (thread) in the JVM that become a zombie
> (not unusual) and when you killed (without -9) the JVM gracefully
> waited for all of it's threads and thereby removed the zombie from the
> system?

I forgot to mention, that the process was running under Solaris 8. The PID
that was claimed to be a zombie was a single javaprocess (not a thread
that had been forked by a parent-process).

Next time, we'll have to try and gdb/strace it, but I wasn't too bright at
2.30AM ;-)

What also came to my mind (And what Jani suggested earlier) is that if
this is the wanted behaviour, why not add a statement such as alertmax or
similar that would limit the amount of alerts monit sends.

> --
> Jan-Henrik Haukeland

        Eetu Rantanen

reply via email to

[Prev in Thread] Current Thread [Next in Thread]