Package: memstat Version: 0.5 Severity: normal In man memstat, one can read
`It is possible to confuse memstat by using mmap in combination with a block-device. In the original version, memstat treated block devices just like any other file, and if you mmap'ed one of them, they would show up on the shared-object list. This worked for mmap'ed hard disks and floppies, but it produced absurd results with block devices like /dev/zero and /dev/mem. As a partial fix, memstat now ignores all mapped block devices, though this may cause memstat to ignore some mem- ory usage.4 Showing the /dev/zero and /dev/mem virtual memory mapping is _not_ absurd, it indeed does take virtual memory to map these, so memstat should show them. As for `We really ought to show some real-memory usage statistics, but it's just not there in /proc.', yes it is now (since something like 2.6.24), see /proc/pid/smaps. Samuel -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages memstat depends on: ii libc6 2.7-13 GNU C Library: Shared libraries memstat recommends no packages. memstat suggests no packages. -- no debconf information -- Samuel «Tiens, quand j'aurai un peu de temps et une partition libre, je crois que je vais essayer de remplacer mes scripts de démarrage par des programmes Windows lancés via Wine et binfmt_misc :-)» -+- AGV in Guide du linuxien pervers - "J'sais pas quoi faire... (air connu)" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
