lastcomm parses acct log file incorrectly (breezy)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
acct (Debian) |
Fix Released
|
Unknown
|
|||
acct (Ubuntu) |
Fix Released
|
Medium
|
Matt Zimmerman |
Bug Description
On the i386 version of breezy on my server, the lastcomm command seems to misparse the acct log file. Everything except the process name looks correct, but the process names themselves in the lastcomm output are gibberish. In the non-human readable log file, you can clearly see the command names in plain-text, yet these are what it's somehow messing up when generating the output. This works properly on the i386 hoary server I run at home.
For example, these are the last lines I get from running lastcomm:
X? root ?? 0.00 secs Thu Jan 1 00:00
?? F 34816 ?? 0.00 secs Thu Jan 1 00:00
?? 34816 ?? 0.00 secs Thu Jan 1 00:00
?? 34816 ?? 0.00 secs Thu Jan 1 00:00
x? S 34816 ?? 0.00 secs Thu Jan 1 00:00
The rest of the output is similarly broken, with not a single correct process name.
and this is the current last chunk of the log file where we can clearly see "sh", "find", "cron" and others. (note that it may not match since it probably added to the log between the time I copied the former and latter):
sh^@^@^
Hello,
I was wondering if GNU acct accounting software is still maintained.
Linux kernel v2.6 has a link for patched accounting software which
supports "account format version 3", and I was wondering if there were
plans to integrate this support into mainline acct.
Thanks,
Justin