Hi all,
> > I think the important point here is if it is POSIX. If it is not
> > then maybe we should think to revert to CLOCK_MONOTONIC.
>
> CLOCK_BOOTTIME is not POSIX, but CLOCK_MONOTONIC is[0]. CLOCK_BOOTTIME
> was added in Linux 2.6.39 and is Linux-specific[1].
>
> Thus, I would be in fav
Dear Roberto,
On 1/17/19 9:42 AM, k...@shike2.com wrote:
> I think the important point here is if it is POSIX. If it is not
> then maybe we should think to revert to CLOCK_MONOTONIC.
CLOCK_BOOTTIME is not POSIX, but CLOCK_MONOTONIC is[0]. CLOCK_BOOTTIME
was added in Linux 2.6.39 and is Linux-sp
> Oops, I misread the diff. Agreed.
Well, my idea wasn't accept the patch (I hate the ifdef there), but
changing the clock used and remove the problem.
Regards,
On Thu, Jan 17, 2019 at 08:42:27AM +, k...@shike2.com wrote:
> > Update your system.
>
>
> I think the important point here is if it is POSIX. If it is not
> then maybe we should think to revert to CLOCK_MONOTONIC.
>
> Regards,
>
>
Oops, I misread the diff. Agreed.
--
Kind regards,
Hilt
> Update your system.
I think the important point here is if it is POSIX. If it is not
then maybe we should think to revert to CLOCK_MONOTONIC.
Regards,
On Wed, Jan 16, 2019 at 07:08:54PM +0100, Alessandro DE LAURENZIS wrote:
> Dear slstatus devs,
>
> CLOCK_BOOTTIME (used in components/uptime.c) is missing on some platforms
> (on RHEL6, for example). I'm not an expert in this field, but for similar
> situations it seems to be a common practice to
Dear slstatus devs,
CLOCK_BOOTTIME (used in components/uptime.c) is missing on some
platforms (on RHEL6, for example). I'm not an expert in this field, but
for similar situations it seems to be a common practice to revert to
CLOCK_MONOTONIC.
Please consider the following patch, which works f
