Hi Martin,
The fact that there is no stop method, doesn't mean that monit will
skip
the service on stop command - the selector 'all' matches all
services
and monit will disable the monitoring of this service.
Monit did skip the service on stop command up until 4.8.2. What you
describe is new behavior that doesn't show up in the change log.
Was this change in behavior requested?
Thanks,
Aaron
-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Martin Pala
Sent: Thursday, November 30, 2006 4:44 PM
To: The monit developer list
Subject: Re: Http/cervlet.c
Aaron Scamehorn wrote:
Hello,
First question: Is this the correct forum for reporting bugs? If
not,
please direct me to the proper forum. Thanks.
Yes
This has introduced the following behavior:
Service setup as Device and/or System get terminated when a "Stop
All"
command is issued. Actually, any service that doesn't have a Stop
Program directive will be stopped anyway.
This is correct behavior. The stop command does two things:
1.) stops the service provided there is stop method
2.) disables the service monitoring (regardless of the stop method
existence)
The fact that there is no stop method, doesn't mean that monit will
skip
the service on stop command - the selector 'all' matches all
services
and monit will disable the monitoring of this service.
You can use service groups (the 'group' statement) to limit the 'stop
all' scope:
monit -g myservices stop all
will then stop just the services in the 'myservices' group.
Martin
_______________________________________________
monit-dev mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/monit-dev
_______________________________________________
monit-dev mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/monit-dev