[Bug 1815177] Re: Wrong system clock causes CA client to spin

[Ralph Lange via Core-talk <core-talk at aps.anl.gov>]

Moved to https://github.com/epics-base/epics-base/issues/455


** Changed in: epics-base
       Status: New => Invalid

** Bug watch added: github.com/epics-base/epics-base/issues #455
   https://github.com/epics-base/epics-base/issues/455

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1815177

Title:
  Wrong system clock causes CA client to spin

Status in EPICS Base:
  Invalid

Bug description:
  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 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
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1815177/+subscriptions