Has anybody here tried the Monit utility (http://mmonit.com/monit/)? I
need to set up some kind of watchdog functionality for a custom
service otherwise started via init (i.e. via a script in /etc/init.d +
rc*.d links managed by chkconfig) and it seems like this system may give
me nearly what
Toralf Lund píše v Pá 11. 06. 2010 v 09:21 +0200:
Has anybody here tried the Monit utility (http://mmonit.com/monit/)? I
need to set up some kind of watchdog functionality for a custom
service otherwise started via init (i.e. via a script in /etc/init.d +
rc*.d links managed by chkconfig)
Pavel Lisý wrote:
Toralf Lund píše v Pá 11. 06. 2010 v 09:21 +0200:
Has anybody here tried the Monit utility (http://mmonit.com/monit/)? I
need to set up some kind of watchdog functionality for a custom
service otherwise started via init (i.e. via a script in /etc/init.d +
rc*.d links
On 11/06/2010 08:21, Toralf Lund wrote:
Has anybody here tried the Monit utility (http://mmonit.com/monit/)?
For what you are trying to do - take a look at God (
http://god.rubyforge.org/ ) instead or : as lesser complex solution -
bluepill ( http://github.com/arya/bluepill )
I've used Monit
I think you are missing my point. This is precisely what I do not want
to do. The last bit here, I mean - i.e. I'm asking for a way to set up
so the rename /etc/monit.d/sshd.conf to something different step won't
be necessary.
Depending on how much effort you are willing to put into this,
Karanbir Singh wrote:
On 11/06/2010 08:21, Toralf Lund wrote:
Has anybody here tried the Monit utility (http://mmonit.com/monit/)?
For what you are trying to do - take a look at God (
http://god.rubyforge.org/ ) instead or : as lesser complex solution -
bluepill (
On 11/06/2010 10:49, Toralf Lund wrote:
That's actually part of what I want to do. I'd like to have an rpm
package install put a real monitoring config in /etc/monitors.d, but I
can't really do it if that means automatically starting the service - it
must be possible (and simple) to install
Geoff Galitz wrote:
I think you are missing my point. This is precisely what I do not want
to do. The last bit here, I mean - i.e. I'm asking for a way to set up
so the rename /etc/monit.d/sshd.conf to something different step won't
be necessary.
Depending on how much effort you are
Karanbir Singh wrote:
On 11/06/2010 10:49, Toralf Lund wrote:
That's actually part of what I want to do. I'd like to have an rpm
package install put a real monitoring config in /etc/monitors.d, but I
can't really do it if that means automatically starting the service - it
must be
I have a feeling that introducing nagios monitoring is a little too
involved, though. I want to distribute the setup to external systems, so
ideally there should be one monitoring package install and a simple
enable command at the most, in addition to installation of the actual
software.
Geoff Galitz wrote:
I have a feeling that introducing nagios monitoring is a little too
involved, though. I want to distribute the setup to external systems, so
ideally there should be one monitoring package install and a simple
enable command at the most, in addition to installation of
On 11/06/2010 12:25, Toralf Lund wrote:
From reading the docs on the web sites, there are a number of things
that are not quite clear, like what the process tests actually do, or
how I might combine a file test (does the pid file xist?) with them (f
that's what I want. This is perhaps
12 matches
Mail list logo
