Bug 1126849 - disrupted sentence in default logwatch.conf file
Summary: disrupted sentence in default logwatch.conf file
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: logwatch
Version: 6.5
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On: 1126848
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-05 12:41 UTC by Martin Frodl
Modified: 2015-10-12 14:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1126848
Environment:
Last Closed: 2015-10-12 14:01:49 UTC


Attachments (Terms of Use)

Description Martin Frodl 2014-08-05 12:41:44 UTC
+++ This bug was initially created as a clone of Bug #1126848 +++

Description of problem:

Starting from line 54, the default config file /usr/share/logwatch/default.conf/logwatch.conf reads:

# Use archives?  If set to 'Yes', the archives of logfiles
# (i.e. /var/log/messages.1 or /var/log/messages.1.gz) will
# be searched in addition to the /var/log/messages file.
# This usually will not do much if your range is set to just
# 'Yesterday' or 'Today'... it is probably best used with
# By default this is now set to Yes. To turn off Archives uncomment this.
#Archives = No
# Range = All

What was probably meant is the following:

# Use archives?  If set to 'Yes', the archives of logfiles
# (i.e. /var/log/messages.1 or /var/log/messages.1.gz) will
# be searched in addition to the /var/log/messages file.
# This usually will not do much if your range is set to just
# 'Yesterday' or 'Today'... it is probably best used with
# Range = All
# By default this is now set to Yes. To turn off Archives uncomment this.
#Archives = No

That is to say, the last line containing '# Range = All' should be placed two lines higher for the text to make sense.


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


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