Help needed: The year is changed to 2034 - more info
Padiyath Sreekumaran <[email protected]>
| Newsgroups | gmane.os.tru64.managers |
|---|---|
| Message-ID | <[email protected]> |
Hello, I have the following information more. The WS is a COMPAQ Alpha WS XP1000. I see in binary file disk the problem already started on Dec 1. since there was an automatic reboot. The user never informed me about this. >From there onwards the year seems to be wrong.In binary.errlog I see the following entry: Logging OS 2. Digital UNIX System Architecture 2. Alpha Event sequence number 0. Timestamp of occurrence 01-DEC-2034 14:16:01 <------------- Host name psw222 System type register x00000022 Systype 34. (Regatta Family) Number of CPUs (mpnum) x00000001 CPU logging event (mperr) x00000000 I would like to know whether I have to reinstall the system or not? In that case I will never know how the year is changed. Sorry for the trouble and thanks in advance. Regards, Kumar -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Padiyath Sreekumaran Sent: Montag, 19. Dezember 2005 16:54 To: [email protected] Subject: Help needed: The year is changed to 2034 Hello, I had a disk crash in one of our Tru64 v5.1A system. So I replaced the disk(it was root, usr partition disk-AdvFS) and restored the files from a backup. (After booting from CD). Now I see that the following directories and many of the files in the directories are having the year 2034(? #ls -l /|grep 2034 lrwxr-xr-x 1 root system 22 Dec 2 2034 .local.. -> cluster/members/{memb} drwxr-xr-x 2 root system 8192 Dec 2 2034 .sysman drwx------ 2 root system 8192 Dec 2 2034 .tags drwxr-xr-x 2 root system 8192 Dec 2 2034 TT_DB lrwxr-xr-x 1 root system 7 Dec 2 2034 bin -> usr/bin drwxr-xr-x 2 root system 8192 Dec 2 2034 cdrom drwxr-xr-x 4 root system 8192 Dec 2 2034 cluster lrwxrwxrwx 1 root system 26 Dec 2 2034 dev -> cluster/members/{memb}/dev drwxr-xr-x 9 root system 8192 Dec 2 2034 devices drwxr-xr-x 2 root system 8192 Dec 2 2034 home1 lrwxr-xr-x 1 root system 7 Dec 2 2034 lib -> usr/lib drwxr-xr-x 2 root system 8192 Dec 2 2034 mdec drwxr-xr-x 2 root system 8192 Dec 2 2034 mnt lrwxrwxrwx 1 root system 8 Dec 2 2034 nsr -> /var/nsr drwxr-xr-x 4 root system 8192 Dec 2 2034 opt drwxr-xr-x 2 root system 8192 Dec 2 2034 progs dr-xr-xr-x 3 root system 8192 Dec 2 2034 psi drwxr-xr-x 10 root system 8192 Dec 2 2034 sbin drwxrwxr-x 2 root system 8192 Dec 2 2034 scratch drwxr-xr-x 2 root system 8192 Dec 2 2034 shlib drwxr-xr-x 2 root system 8192 Dec 2 2034 subsys drwxr-xr-x 3 root system 8192 Dec 2 2034 sys drwxr-xr-x 5 root system 8192 Dec 2 2034 tcb drwxr-xr-x 2 root system 8192 Dec 2 2034 threadsafe lrwxrwxrwx 1 root system 26 Dec 2 2034 tmp -> cluster/members/{memb}/tmp drwxr-xr-x 24 root system 8192 Dec 2 2034 var How it can happen? How can I change the year? Whether I have to again do a recover from the tape? I have not yet looked on the tape contents. The following files are having correct date: # ls -l /vm* -rwxr-xr-x 1 root system 19047936 Jul 8 2002 /vmunix -rwxr-xr-x 1 root system 16660528 Jul 8 2002 /vmunix.PrePatch -rwxr-xr-x 1 root system 16825616 Jul 8 2002 /vmunix.orig How can I solve this problem? I will very much appreciate for a fast suggestion. Regards, Kumar ------------------------------------------------------------------ Padiyath Sreekumar | Tel: +41.56.310.3643 Paul Scherrer Institut | email: [email protected] AIT | Office: WHGA/U132 WHGA/U132 | Fax: +41.56.310.3649 CH-5232 Villigen PSI | Switzerland | -----------------------------------------------------------------