Bug 155286 - Long mount points in df output of logwatch drop info
Long mount points in df output of logwatch drop info
Status: CLOSED DUPLICATE of bug 138285
Product: Fedora
Classification: Fedora
Component: logwatch (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jiri Ryska
Depends On:
  Show dependency treegraph
Reported: 2005-04-18 15:39 EDT by Lamont Peterson
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-19 06:30:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lamont Peterson 2005-04-18 15:39:39 EDT
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): 
How reproducible: 
Additional info: 
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.
Comment 1 Jiri Ryska 2005-04-19 06:30:26 EDT

*** This bug has been marked as a duplicate of 138285 ***

Note You need to log in before you can comment on or make changes to this bug.