it's because of OpenBSD which uses always 64-bit time_t even on 32-bit
platforms since OpenBSD 5.5 (used for process starttime)
On 10 Feb 2015, at 21:34, Rory Toma r...@trs80.net wrote:
Thanks. In xml.c, is there any reason that is has to be a (long long)?
On 2/9/15 9:48 AM, Martin Pala
Thanks. In xml.c, is there any reason that is has to be a (long long)?
On 2/9/15 9:48 AM, Martin Pala wrote:
On 06 Feb 2015, at 15:03, Rory Toma r...@trs80.net wrote:
On 2/6/15 2:45 AM, Martin Pala wrote:
Hi Rory,
Monit reports process uptime in minutes since Monit 5.4. There is also uptime
On 06 Feb 2015, at 15:03, Rory Toma r...@trs80.net wrote:
On 2/6/15 2:45 AM, Martin Pala wrote:
Hi Rory,
Monit reports process uptime in minutes since Monit 5.4. There is also
uptime test, example:
check process myapp with pidfile /var/run/myapp.pid
start program =
The delay isn't optimal for me, as it is a non-deterministic time that I
have to deal with, and boot time is of importance. thanks.
On 2/6/15 9:56 AM, Sean Penticoff wrote:
you can set a delay for startup in monit
## Start Monit in the background (run as a daemon):
#
set daemon 120
Hi Rory,
Monit reports process uptime in minutes since Monit 5.4. There is also uptime
test, example:
check process myapp with pidfile /var/run/myapp.pid
start program = /etc/init.d/myapp start
stop program = /etc/init.d/myapp stop
if
Hi Rory,
The ps command lets you define an output format.
The 'time' in it is the CPU time used by the process.
More interrestingly, there is 'etime' and 'etimes' formats, which help you
with what you want to do.
ps -o etimes `pgrep apache2 -u root`
Will give you the apache2 root process age
On 2/6/15 2:45 AM, Martin Pala wrote:
Hi Rory,
Monit reports process uptime in minutes since Monit 5.4. There is also uptime
test, example:
check process myapp with pidfile /var/run/myapp.pid
start program = /etc/init.d/myapp start
stop program =
you can set a delay for startup in monit
## Start Monit in the background (run as a daemon):
#
set daemon 120 # check services at 1-minute intervals
with start delay 240# optional: delay the first check by
4-minutes (by
we have a service that runs on first boot that
Is there a good way for monit to report actual uptime on processes and
itself that is not based on the date, but rather the actual passage of time?
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
