Re: Plans for the next release

[Jan-Henrik Haukeland]

address@hidden writes:

> no. 2 Sounds like we are reinventing the wheel.  I though monit was supposed
> to monitor ?  Sounds a bit like feature creep and this is difficult to do
> cross platform.  init works.

Actually this was a bad title. My understanding of this was not so
much as to replace init as to make it easier to manage programs like
init does. From the monit web-page:

  Two new directives will be added which makes monit read a script and
  a pid file directory. In this case the start, stop and with pidfile
  statements are not necessary and program entries are simplified to
  (example for SYS V systems):
 
    set program-directory /etc/init.d/ 
    set pidfile-directory /var/run

    check crond ..
    check syslogd and alert on {restart} ..

you know how you today have to tell monit where the start/stop and
pidfile is. Like

 check httpd with pidfile /var/run/httpd.pid
  start = "/etc/init.d/httpd start"
  stop = "/etc/init.d/httpd stop"

But by setting a predefined pidfile and script directory you can write
the above as:

  check httpd

(Whenever monit sees such a reduced check-statement it will implicitly
use the global set directory statements to add: pidfile=/var/run/httpd
and start/stop= /etc/init.d/http start/stop)


> Please don't get me wrong - I think monit is great as a process watchdog
> tool - and I love he small tool that do a small thing well unix mentality.
> Hence my worry of feature creap.  Concentrate on monit(oring) and avoid
> reinventing init.   There be dragons (and init just works!)

Absolutely, To replace init is not a good idea in my book either. I
want monit to run on as much unix systems as possible and do
monitoring good not much more.

-- 
Jan-Henrik Haukeland