Red Hat Bugzilla – Bug 155286
Long mount points in df output of logwatch drop info
Last modified: 2007-11-30 17:11:04 EST
Description of problem:
In the default logwatch output, df is run and the output included. If the
mount points are just a little too long, then the information to be reported
is dropped. This is *not* happening when you run df yourself.
Here is an example:
------------------ Disk Space --------------------
/dev/mapper/vg0-root Â 512M Â 257M Â 256M Â 51% /
/dev/hda1 Â Â Â Â Â Â Â 99M Â 16M Â 79M Â 17% /boot
/dev/mapper/vg0-home Â 10G Â 7.3G Â 2.8G Â 73% /home
/dev/mapper/vg0-usr Â Â 10G Â 5.0G Â 5.1G Â 50% /usr
/dev/mapper/vg0-var Â 5.0G Â 1.3G Â 3.8G Â 25% /var
/dev/mapper/vg0-opt Â 256M Â 59M Â 198M Â 23% /opt
/dev/mapper/vg0-tmp Â 512M Â 34M Â 479M Â 7% /tmp
Version-Release number of selected component (if applicable):
This is happening on all the FC3 boxes I have (i386 & AMD64).
This did not occur with FC2 or on RHEL3. I have not tried it on RHEL4, yet,
but can if you would like me to.
*** This bug has been marked as a duplicate of 138285 ***