Bug 141579
| Summary: | logwatch truncates file system usage output | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Antonin Mares <antonin.mares> |
| Component: | logwatch | Assignee: | Jiri Ryska <jryska> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-02-21 19:07:27 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I have the same problem. I think the issue is in zz-disk_space, where it executes: df -h | grep '^/dev/' If you wanted to remove the tmpfs entries (which start with "none" in the listing above), then the following would work: df -h -x tmpfs *** This bug has been marked as a duplicate of 138285 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Description of problem: In email recieved every night from logwatch I don't see space usage for one filesystem. Output from logwatch looks like this: ------------------ Disk Space -------------------- /dev/sda1 251M 101M 137M 43% / /dev/sda2 2.0G 487M 1.4G 26% /usr /dev/sda5 494M 92M 378M 20% /var /dev/mapper/datavg-ftplv The "df" command gives me following output: Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 256666 106759 136655 44% / none 257320 0 257320 0% /dev/shm /dev/sda2 2063536 503688 1455024 26% /usr /dev/sda5 505604 93212 386288 20% /var /dev/mapper/datavg-ftplv 940651248 1927284 890941668 1% /var/ftp Version-Release number of selected component (if applicable): logwatch-5.2.2-1 How reproducible: Didn't try Steps to Reproduce: Additional info: