Wrong system clock causes CA client to spin

On 2/8/19 1:48 AM, Ralph Lange wrote:
> Public bug reported:
>
> Using EPICS 7.0.2 on a Linux box with a system clock that was set to the
> Posix epoch (NULL) by an irresponsible time synchronization daemon, use
> of a simple CA client sends it into a fast infinite loop printing

Can you get a stack trace of where ClockTimeGetCurrent()
is being called from (via. epicsTimeGetCurrent() )?

I would be curious to know if use of the monotonic clock would help.

https://code.launchpad.net/~epics-core/epics-base/+git/Com/+merge/361380

> errors:
>
> [me@my_box]$ caget TEST-HLT-SYSM-4503-IC:PCF0001-PROCSTS
> WARNING: OS Clock pre-dates the EPICS epoch!
> Using 1990-01-02 00:00:00.000000 UTC
> WARNING: OS Clock pre-dates the EPICS epoch!
> Using 1990-01-02 00:00:00.000000 UTC
> WARNING: OS Clock pre-dates the EPICS epoch!
> Using 1990-01-02 00:00:00.000000 UTC
> WARNING: OS Clock pre-dates the EPICS epoch!
> Using 1990-01-02 00:00:00.000000 UTC
> WARNING: OS Clock pre-dates the EPICS epoch!
> Using 1990-01-02 00:00:00.000000 UTC
> WARNING: OS Clock pre-dates the EPICS epoch!
> Using 1990-01-02 00:00:00.000000 UTC
> WARNING: OS Clock pre-dates the EPICS epoch!
> Using 1990-01-02 00:00:00.000000 UTC
> WARNING: OS Clock pre-dates the EPICS epoch!
> Using 1990-01-02 00:00:00.000000 UTC
> WARNING: OS Clock pre-dates the EPICS epoch!
> Using 1990-01-02 00:00:00.000000 UTC
> WARNING: OS Clock pre-dates the EPICS epoch!
> Using 1990-01-02 00:00:00.000000 UTC
> ...
>
> ** Affects: epics-base
> Importance: Undecided
> Status: New
>
>
> ** Tags: ca catools
>