Package: acct
Version: 6.3.5-39
Severity: important

In our alpha machine, lastcomm prints somewhat unusual dates, 
although the PC's clock seems to work well. The following is a sample
outpt:

# date; lastcomm |head -5
Wed Jan 19 11:00:30 JST 2005
date                    root     stderr     0.00 secs Fri Feb 14 21:25
lastcomm              X root     stderr     0.03 secs Sun Dec  1 20:36
head                    root     stderr     0.00 secs Tue Jan  8 14:57
date                    root     stderr     0.00 secs Fri Feb 14 21:25
lastcomm                root     stderr     0.00 secs Mon Feb  2 04:12
# date; lastcomm |head -5
Wed Jan 19 11:00:31 JST 2005
date                    root     stderr     0.00 secs Fri Feb 14 21:25
lastcomm              X root     stderr     0.03 secs Thu Jan  8 03:04
head                    root     stderr     0.00 secs Tue Jan  8 14:57
date                    root     stderr     0.00 secs Fri Feb 14 21:25
lastcomm              X root     stderr     0.03 secs Sun Dec  1 20:36
# date; lastcomm |head -5
Wed Jan 19 11:00:33 JST 2005
date                    root     stderr     0.00 secs Sat May 11 06:25
lastcomm              X root     stderr     0.03 secs Mon Apr 11 09:43
head                    root     stderr     0.00 secs Sun Jan 21 08:09
date                    root     stderr     0.00 secs Fri Feb 14 21:25
lastcomm              X root     stderr     0.03 secs Thu Jan  8 03:04
#

Hence the lastcomm command provides any meaningful infomation.

In other architectures (i386, ppc), lastcomm works well.


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: alpha
Kernel: Linux 2.4.27-1-generic
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages acct depends on:
ii  debconf                     1.4.30.11    Debian configuration management sy
ii  libc6.1                     2.3.2.ds1-20 GNU C Library: Shared libraries an

-- debconf information:
  acct/kernel_mismatch: false


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to