Monit start delay affects http daemon and cli interface

[Jef Driesen]

A start delay specified in the config file with:

set daemon <seconds> with start delay <seconds>

does not only delay the monitoring, but also the startup of the http daemon. That prevents the use of the monit CLI interface during this time period:

# monit summary
Cannot create socket to [localhost]:2812 -- Cannot create socket to [::1]:2812 -- Address family not supported by protocol

This is easily fixed by only delaying the monitoring. The attached patch does that.

[Tildeslash]

Hello Jef, thank you for patch - the problem is, that the “start delay” is often used in the context, where the network interface is not ready yet (so the monit http interface won’t be able to bind if it’s set to specific IP).

We have modified the “start delay” behaviour - the original intent was to delay on reboot only, the delay on each start is kind of overkill. The patch was checked in for issue #829 (https://bitbucket.org/tildeslash/monit/commits/1143ccd3d37d).