Bug 1293621 - Should not change the case of $logdir
Summary: Should not change the case of $logdir
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: logwatch
Version: 6.7
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: Martin Frodl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-22 12:59 UTC by Martin Frodl
Modified: 2016-01-11 13:23 UTC (History)
2 users (show)

Fixed In Version: logwatch-7.3.6-54.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 205104
Environment:
Last Closed: 2016-01-11 13:23:43 UTC
Target Upstream Version:

Attachments (Terms of Use)
patch (651 bytes, patch)
2016-01-04 13:00 UTC, Jan Synacek 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1293624 0 unspecified CLOSED Should not change the case of $logdir 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2016:0020 0 normal SHIPPED_LIVE logwatch bug fix update 2016-01-11 18:23:07 UTC

Internal Links: 1293624

Description Martin Frodl 2015-12-22 12:59:32 UTC 
Description of problem:

The issue described below, which was fixed years ago as bug 205104 in RHEL 4, still persists in RHEL 6. Tested with the --logdir command-line option as well as the LogDir configuration directive.

Version-Release number of selected component (if applicable):
logwatch-7.3.6-52.el6.noarch

+++ This bug was initially created as a clone of Bug #205104 +++

If you have $logdir=/XXX in your logwatch.conf then it will instead try to
access /xxx.  Currently the only way to access logs in a directory that contains
capital letters seems to be creating a symlink with only lowercase letters.  EG
"ln -s /XXX /xxx".
Comment 2 Jan Synacek 2016-01-04 13:00:05 UTC 
Created attachment 1111479 [details]
patch
Comment 8 errata-xmlrpc 2016-01-11 13:23:43 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0020.html
Note You need to log in before you can comment on or make changes to this bug.