[Info-vax] Leap year and Set Time/Cluster problem

Scott Greig jsgreig at geminaq.com
Thu Mar 1 08:52:59 EST 2012


There seems to be a problem with $ Set Time/Cluster.
Last night (Feb 29th) at 10:30 pm, a $ Set Time/Cluster
was issued.  As a result, each node's time was reset to
Feb 28th, 10:30.  Here is the accounting entry for the
offending SET TIME command:

SET Image Termination
---------------------
Username:          SYSTEM            UIC:
[SYSTEM]
Account:           SYSTEM            Finish time:       28-FEB-2012
22:30:00.00  <----Yikes
Process ID:        20233624          Start time:        29-FEB-2012
22:30:00.45
Owner ID:                            Elapsed time:              ***
00:00:00.45
Terminal name:                       Processor time:              0
00:00:00.00
Remote node addr:                    Priority:          3
Remote node name:                    Privilege <31-00>: BFFFFFFF
Remote ID:                           Privilege <63-32>: FFFFFFFF
Remote full
name:
Posix UID:         -2                Posix GID:         -2
(%XFFFFFFFE)
Queue entry:       2338              Final status code: 10000001
Queue name:       nodename_BATCH
Job name:          SETTIME
Final status text: %SYSTEM-S-NORMAL, normal successful completion
Page faults:               31        Direct IO:                  1
Page fault reads:           3        Buffered IO:                0
Peak working set:        2992        Volumes mounted:            0
Peak page file:          6560        Images executed:            1

Image name: $1$DGA100:[SYS0.SYSCOMMON.][SYSEXE]SET.EXE

I will be reporting this to HP this morning.

Scott



More information about the Info-vax mailing list