From: "Troy Curtis Jr" <troycurtisjr@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Practical log reviewing
Date: Tue, 22 Aug 2006 21:04:14 -0500 [thread overview]
Message-ID: <4148457f0608221904r696c33a8r9780987210f99a29@mail.gmail.com> (raw)
In-Reply-To: <49bf44f10608220816q5d6ca1atdd8966a262b050de@mail.gmail.com>
Logwatch is really designed to be run as a cronjob which sends you an
email after it has parsed through your logs. The configuration for
logwatch is located in the /etc/log.d/ directory. In that directory
you will find many scripts and configuration options for a wide range
of different log files. You will want to start with
/etc/log.d/conf/logwatch.conf. By default it send the email message
with the log analysis to root (you can set it to whatever you like if
you have your mailer configured correctly).
You should probably get a meaningful analysis with all the defaults,
just check your root accounts mail.
I have been using logwatch for many months now and have been very
happy with it. Hope this helps point you in the right direction.
(Also check /etc/cron.daily/logwatch for the default cronjob).
Troy
BTW the obfuscated perl email address that gentux uses has to be the
coolest sig ever!
On 8/22/06, Grant <emailgrant@gmail.com> wrote:
> > > Does anyone know of a practical way to review all the various logs on
> > > the system each day? Does it just come down to a brisk scroll through
> > > the previous day's rotated logs?
> > >
> >
> > Isn't that why logwatch was created?
>
> I emerged logwatch, but even though the man pages reference the
> command 'logwatch' it is a 'command not found'. I ran 'logwatch.pl'
> which I spotted from the emerge's output, but there was no ouput from
> that script at all.
>
> - Grant
> --
> gentoo-user@gentoo.org mailing list
>
>
--
"Beware of spyware. If you can, use the Firefox browser." - USA Today
Download now at http://getfirefox.com
Registered Linux User #354814 ( http://counter.li.org/)
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-23 2:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 3:18 [gentoo-user] Practical log reviewing Grant
2006-08-22 3:50 ` Collins Richey
2006-08-22 15:16 ` Grant
2006-08-23 2:04 ` Troy Curtis Jr [this message]
2006-08-23 3:11 ` Michael Sullivan
2006-08-22 3:53 ` gentuxx
2006-08-22 4:57 ` [gentoo-user] " reader
2006-08-22 8:16 ` Stefan Wimmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4148457f0608221904r696c33a8r9780987210f99a29@mail.gmail.com \
--to=troycurtisjr@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox