Bug 40000

Informational

GemStone/S 64 Bit

2.3.1.6, 2.3.1, 2.3, 2.2.5.4, 2.2.5.3, 2.2.5.2, 2.2.5.1, 2.2.5, 2.2.x, 2.2, 2.1.5, 2.1.4, 2.1.x, 2.1

All

n/a

SIGTERM log message in seconds offset rather than DateTime

When a SIGTERM is sent to a process, this is recorded in the
process log with something similar to:

  GS Signal Handler: Signal 15, SIGTERM, Software Termination Signal
  Received at 1242925247 in thread 1

The timestamp is printed in the internal time, which is seconds
offset since January 1, 1970.  This is not translated into a
readable timestamp, to avoid the small risk of system calls
deadlocking as a result of that processing.

Workaround

To translate the seconds offset into a DateTime, use the following expression:

(DateTime fromStringGmt: '01/01/1970 00:00:00') addSeconds: <secondsOffset>

This will give you the time in GMT, which you may then need to
translate into your local time.


Last updated: 7/1/09