[Description] lastcomm on IA64 command shows wrong elapsed time (10.24 times bigger than time command value) as follow: # time dd if=/dev/zero of=file bs=1024 count=3000 3000+0 records in 3000+0 records out real 0m0.050s user 0m0.004s sys 0m0.047s # lastcomm dd dd root stdout 0.50 secs Mon Aug 16 03:33 Customer cannot do accounting his system correctly. This gives the serious impact to his system's security and/or management. [Environment] RHEL 3 AS IPF - kernel-2.4.21-15.EL - glibc-kernheaders-2.4-8.32 - psacct-6.3.2-27 [Additional Info] This seems to be caused by mismatching between kernel's frequency (HZ = 1024) and accounting's (HZ = 100) on IA64. in /usr/src/linux-2.4/include/asm-ia64/param.h: #define HZ 1024 in /usr/include/linux/acct.h: #define AHZ 100 If AHZ is set as 1024 and re-build psacct package, then lastcomm shows correct value. Similar bug has been reported at BZ#114617, 89959. [Environment] RHEL 3 AS IPF - kernel-2.4.21-15.EL - glibc-kernheaders-2.4-8.32 - psacct-6.3.2-27
BZ 117817 is the same bug, except for RHEL2.1
BZ117817 contains patch.
Erratum RHBA-2004:497-03
Moving back to ASSIGNED as this issue will not be resolved in RHBA-2004:497.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-211.html