Bug 749438 - Save to file option doesn't work in F15
Summary: Save to file option doesn't work in F15
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: logwatch
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Frank Crawford
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-27 03:47 UTC by Ian Mortimer
Modified: 2011-10-31 03:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-31 03:18:30 UTC
Type: ---


Attachments (Terms of Use)

Description Ian Mortimer 2011-10-27 03:47:21 UTC
Description of problem:

It used to be possible to configure /etc/logwatch/conf/logwatch.conf to have logwatch save it's output to a file instead of mailing to root.  That no longer works in F15.


Version-Release number of selected component (if applicable):
logwatch-7.3.6-70.20110203svn25.fc15.noarch

How reproducible:
Always


Steps to Reproduce:
1. install logwatch in F15
2. configure to save to file
3. run logwatch
  
Actual results:
Output is mailed to root and not saved to file.


Expected results:
Output should be saved to the configured file as in previous versions.


Additional info:

In previous versions to save logwatch output to a file required this line in /etc/logwatch/conf/logwatch.conf:

Save "/path/to/file"

That doesn't work in F15 but does in Fedora 14 (logwatch-7.3.6-60) and EL 6 (logwatch-7.3.6-49) and earlier. 

Comments in /usr/share/logwatch/default.conf/logwatch.conf suggest that this should work:

Output = file
Filename = /path/to/file

but that doesn't work either.

The best I can do is set MailTo to null, which sends output to stdout instead of mailing it but that's not the same as the previous behaviour.

Comment 1 Frank Crawford 2011-10-27 09:55:05 UTC
Unlike earlier versions /etc/cron.daily/0logwatch includes specific command-line options that include "--output mail" which then override those in the various configuration files.

If you change these options, does this do what you want?

Comment 2 Ian Mortimer 2011-10-31 03:18:12 UTC
Yes that works.  Also with the "OPTIONS=" line commented out in the cron script, the configuration file options are now working as documented. 


Thanks
--
Ian


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