This doesn't appear to be a problem in glibc at all since it isn't
responsible for reading the records. It looks like the kernel interface
fails to provide a clean way to detect the format, so you simply have to
know a priori that you are not on an ancient kernel that still uses the
old format.
** Changed in: glibc (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/56188
Title:
Wrong implementation of sys_acct() linux-syscall. Discrepancies
between kernel-space & user-space.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/56188/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
