Re: Before I fix this

[Martin Pala]

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 <address@hidden> 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 wrote:
>>> On 06 Feb 2015, at 15:03, Rory Toma <address@hidden> 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 = "/etc/init.d/myapp start"
>>>>                    stop program = "/etc/init.d/myapp stop"
>>>>                    if uptime > 3 days then restart
>>>> 
>>>> Regards,
>>>> Martin
>>>> 
>>>> 
>>>>> On 06 Feb 2015, at 00:28, Rory Toma <address@hidden> wrote:
>>>>> 
>>>>> 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
>>>> --
>>>> To unsubscribe:
>>>> https://lists.nongnu.org/mailman/listinfo/monit-general
>>> SO here's what happens. If monit starts before the time is set, when I run 
>>> monit status, monit will report that it has been running for 45 years. 8-)
>> 
>> Fixed in the development version, will be part of next Monit release (5.12)
>> 
>> 
>> Cheers :)
>> Martin
>> 
>> 
>> --
>> To unsubscribe:
>> https://lists.nongnu.org/mailman/listinfo/monit-general
> 
> 
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general