Logwatch Update

[Julian Field]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Steve Campbell wrote:
>
> ----- Original Message ----- From: "Ken A" <ka at pacific.net>
> To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
> Sent: Wednesday, October 04, 2006 11:30 AM
> Subject: Re: Logwatch Update
>
>
>>
>> Steve Campbell wrote:
>>>
>>> ----- Original Message ----- From: "Ryan Weaver" <ryanw at falsehope.com>
>>> To: "'MailScanner discussion'" <mailscanner at lists.mailscanner.info>
>>> Sent: Wednesday, October 04, 2006 7:08 AM
>>> Subject: RE: Logwatch Update
>>>
>>>
>>>> ----Original Message----
>>>> From: Mike Tremaine
>>>> Sent: Tuesday, October 03, 2006 11:20 PM
>>>> To: mailscanner at lists.mailscanner.info
>>>> Subject: RE: Logwatch Update (Phil Udel)
>>>>
>>>> <snip>
>>>>
>>>>> Or you can always get in out of cvs at logwatch.org. Having said
>>>>> that I'll see if I can roll your changes into the current version.
>>>>> I'd also encourge you [and everyone who uses logwatch] to upgrade
>>>>> to the 7.3.1 release it.
>>>>>
>>>>> -Mike
>>>>
>>>> If you are running RedHat or CentOS, the Razor's Edge RPM 
>>>> Repository keeps
>>>> logwatch fairly up to date.... http://rpm.razorsedge.org/
>>>>
>>>> Thanks,
>>>> Ryan
>>>>
>>>> -- 
>>> I just upgraded the logwatch on my CentOS 3 machine from the link 
>>> above. A general pair of questions about all of this:
>>>
>>> 1. I run the cron.daily logwatch and would like to email myself when 
>>> this is run. Cron seems to want to run this and mail to root. I 
>>> changed the logwatch.conf file (in a few different places) to 
>>> "mailto" my address, but it still mails to root. Anyone know which 
>>> of the four or five logwatch.conf files will correct this?
>>
>> Add this above the logwatch cron job in your root crontab:
>> MAILTO="you at yourdomain.com"
>
> I'm not sure if this is the cron variable you're speaking of or not, 
> but I don't understand where you are suggesting the line should be 
> inserted. This job is run from cron.daily on a RH system, using a Perl 
> script that sets a lot of variables within that script. There is a 
> line to change the logwatch variable "mailto", but that doesn't seem 
> to work. The script runs through all of the 4 default directories to 
> set variables as described in the man page.
>
> The big problem is that when I set the mailto variable in the script 
> using myname at mydomain.com, it indicates a bad variable due to the "@". 
Put a \ before the @

> I tried using another form, along with a Perl string, and that doesn't 
> work either. I think I'll try the /etc/logwatch/conf files and see 
> where I go with that.
>
> Thanks, though
>
> Steve
>>
>> Ken A.
>> Pacific.Net
>>
>>
>>>
>>> 2. If I upgraded, what do I do with the file attached in the earlier 
>>> posts? I do see ClamAV and other new stuff in the report, but will 
>>> the attached file make a difference in what I get with the 
>>> off-the-shelf RPM from above?
>>>
>>> Thanks
>>>
>>> Steve
>>>
>> -- 
>> MailScanner mailing list
>> mailscanner at lists.mailscanner.info
>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>
>> Before posting, read http://wiki.mailscanner.info/posting
>>
>> Support MailScanner development - buy the book off the website! 
>
>

Jules

- -- 
Julian Field
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
For all your IT requirements visit www.transtec.co.uk


-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.5.0 (Build 1112)
Comment: Fetch my public key foot-print from www.mailscanner.info
Charset: ISO-8859-1

wj8DBQFFI+pYEfZZRxQVtlQRAlGZAJsEB8dMhzXQ+bI0x2zdK2WqHHqXYQCgusVF
SAEHgSFpLLHfiUDeJz8NYNU=
=PYSs
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
For all your IT requirements visit www.transtec.co.uk