Bug 189638
Summary: | logwatch does not handle the --logdir option correctly | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Allegro Consultants <support> |
Component: | logwatch | Assignee: | Ivana Varekova <varekova> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | support |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-04-24 15:29:40 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: |
Description
Allegro Consultants
2006-04-21 22:33:15 UTC
The --logdir option seems to be right in your example. Logwatch go through files '/var/log/httpd/tmp/log/httpd/access_log' and '/var/log/httpd/tmp/httpd/*access_log' the logdir is set to 'var/log/httpd/tmp' but the parsed files are 1/ 'log/httpd/access_log' - file '/httpd/access_log' which is in LogFile was not found in /var/log/httpd/tmp/, so logwatch use 'log/httpd/access_log' (this is only done for log_file_names which represent files existing in /var/log dir) and 2/ 'httpd/*access_log' ('/var/log/httpd/*access_log' is not file. Logwatch does not add string log.) - log file names are set in /etc/log.d/conf/logfiles/http.conf (LogFile variable). There is necessary to add the relative path to given logdir path becouse of different services has log files in various subdirectories. So if you want to display logwatch output relevant to all services you can set only one logdir path. Logwatch supposes that the log files directory has the same structure as /var/log directory. If there is any problem, please reopen this bug. Thanks for the explanation. I gather, therefore, that the directory specified with the "--logdir" option on the command line is a *relative* path, not an *absolute* path. That is, logwatch will use the specified directory as a "starting point" for finding log files, rather than look for log files exactly where I tell it, and nowhere else. That's fine. I can live with that, and adjust. However, the man page on this subject is vague, and does not make it clear that the directory specified with the "--logdir" option will be used as an alternate "root" path for logwatch, and that a directory heirarchy with the same structure as /var/log is expected. Therefore, can we change this to a documentation bug, and get the man page written more clearly? |