1 |
Logwatch is really designed to be run as a cronjob which sends you an |
2 |
email after it has parsed through your logs. The configuration for |
3 |
logwatch is located in the /etc/log.d/ directory. In that directory |
4 |
you will find many scripts and configuration options for a wide range |
5 |
of different log files. You will want to start with |
6 |
/etc/log.d/conf/logwatch.conf. By default it send the email message |
7 |
with the log analysis to root (you can set it to whatever you like if |
8 |
you have your mailer configured correctly). |
9 |
|
10 |
You should probably get a meaningful analysis with all the defaults, |
11 |
just check your root accounts mail. |
12 |
|
13 |
I have been using logwatch for many months now and have been very |
14 |
happy with it. Hope this helps point you in the right direction. |
15 |
(Also check /etc/cron.daily/logwatch for the default cronjob). |
16 |
|
17 |
Troy |
18 |
|
19 |
BTW the obfuscated perl email address that gentux uses has to be the |
20 |
coolest sig ever! |
21 |
|
22 |
|
23 |
On 8/22/06, Grant <emailgrant@×××××.com> wrote: |
24 |
> > > Does anyone know of a practical way to review all the various logs on |
25 |
> > > the system each day? Does it just come down to a brisk scroll through |
26 |
> > > the previous day's rotated logs? |
27 |
> > > |
28 |
> > |
29 |
> > Isn't that why logwatch was created? |
30 |
> |
31 |
> I emerged logwatch, but even though the man pages reference the |
32 |
> command 'logwatch' it is a 'command not found'. I ran 'logwatch.pl' |
33 |
> which I spotted from the emerge's output, but there was no ouput from |
34 |
> that script at all. |
35 |
> |
36 |
> - Grant |
37 |
> -- |
38 |
> gentoo-user@g.o mailing list |
39 |
> |
40 |
> |
41 |
|
42 |
|
43 |
-- |
44 |
"Beware of spyware. If you can, use the Firefox browser." - USA Today |
45 |
Download now at http://getfirefox.com |
46 |
Registered Linux User #354814 ( http://counter.li.org/) |
47 |
-- |
48 |
gentoo-user@g.o mailing list |