Re: [Logwatch] Fwd: Default to STDOUT: is it really a good thing?
Mike Tremaine <[email protected]>
| Newsgroups | gmane.comp.log.logwatch.devel |
|---|---|
| Message-ID | <[email protected]> |
Bob Hutchinson wrote: > On Saturday 26 May 2007 7:47 pm, Hugo van der Kooij wrote: >> On Sat, 26 May 2007, Kirk Bauer wrote: >>> More dissenters... I am not sure I understand his problem... but I've >>> never used the HTML format either. >> For starters. When log watch is sending it's own email the subjct is: >> Subject: Logwatch for faramir.hugo.vanderkooij.org (Linux) >> >> But with the crontab output it reads: >> Subject: Cron <root@faramir> /usr/sbin/logwatch >> >> Or something similar. The first one (old style) makes a lot more sense. > > I agree. > > Also, anything coming from cron is "something that went wrong" (apart from > debugging) and I have my incoming mail filtered accordingly. > > my 2p worth > I wasn't a big fan of the change either but I don't think it is that big of a deal. Yes most Logwatch installs use email as the output method. Still most install are also default Redhat/Fedora rpms, they can set the default back to email in their rpm no problem. Anyone who is installing by hand can probably take the extra 10 secs to switch to email default once they get everything they way they want it. Getting HTML output it actually looking pretty good these days, I did a dist.conf especially for the Endian Firewall project and I really like the way it turned out. In this case it is not email but a saved file in HTML. I think we will start seeing more of these types of deployments. So the argument that we've always done email it should be email forever doesn't really sway me that much. Even though the first thing I'll do when I update logwatch is switch it back to email default :). -Mike PS - I was in Washington D.C the last 2 weeks so hopefully I'll get moving on the commandline API Monday morning.