2017-04-13 9:56 GMT+02:00 Sergey B Kirpichev <skirpic...@gmail.com>:
> On Thu, Apr 13, 2017 at 12:12:37AM +0200, Christian Göttsche wrote:
>> 2017-04-12 20:22 GMT+02:00 Sergey B Kirpichev <skirpic...@gmail.com>:
>> > tags 857863 +moreinfo
>> > thanks
>> >
>> > On Wed, Apr 12, 2017 at 05:50:51PM +0200, Christian Göttsche wrote:
>> >> Updated version, similar to the upstream[1] one:
>> >
>> > Are you ready to support monit in systemd-enabled configurations?
>>
>> What do you mean by that?
>
> I mean - will you write guide for users on how to fix default
> systemd configuration to not conflict with monit? Will you
> debug and fix systemd-related issues, if they appear in bts?
I am using the default systemd configuration, but maybe I do not use
the full range of features of monit, cause I do not experience any
conflicts yet.
My main reason to use monit, is to monitor and constrain (resource
wise) daemons, network and filesystems.
For example irqbalance:
<snip>
## irqbalance
#
# monit 5.20
#
check process irqbalance matching "^/usr/sbin/irqbalance "
start program = "/bin/systemctl start irqbalance"
stop program = "/bin/systemctl stop irqbalance"
restart program = "/bin/systemctl restart irqbalance"
if changed PID then alert
if changed PPID then alert
if failed uid "root" then restart
if failed euid "root" then restart
if failed gid "root" then restart
if children != 0 then restart
if threads != 1 then alert
if threads > 10 for 2 cycles then restart
if totalcpu > 1% for 2 cycles then alert
if totalcpu > 10% for 2 cycles then restart
if totalmem > 4 MB for 2 cycles then alert
if totalmem > 30 MB for 2 cycles then restart
if 3 restarts within 7 cycles then stop
group server
</snip>
I might be able to help with systemd related issues but I can not
promise anything.
