On Tue, Dec 7, 2010 at 10:05, Tom Horsley wrote:
> On Tue, 7 Dec 2010 09:46:10 -0800
> Donald Russell wrote:
>
> > Now that I've actually done it once, it seems pretty simple... so why did
> it
> > appear so complicated in the doc? hmmm.
>
> Well, what gets me (and still does I think) is the utte
On Tue, 7 Dec 2010 09:46:10 -0800
Donald Russell wrote:
> Now that I've actually done it once, it seems pretty simple... so why did it
> appear so complicated in the doc? hmmm.
Well, what gets me (and still does I think) is the utter inability
to guess which logfiles get processed for which servi
---
Hey! Hey! You! You! Get off of my cloud!
http://news.cnet.com/8301-13578_3-20002423-38.html
On Fri, Dec 3, 2010 at 14:25, Rich Mahn wrote:
> Donald Russell wrote:
>
> >I have an application that uses the logger -t command to add
> >specific messages in /var/log/messages. I'd like
Donald Russell wrote:
>I have an application that uses the logger -t command to add
>specific messages in /var/log/messages. I'd like to add those in a
>section of it's own in the logwatch report but am having trouble
>following the information in /usr/share/doc/logwatch-7.3 in t
On Fri, 3 Dec 2010 09:34:35 -0800
Donald Russell wrote:
> What did I miss?
You certainly didn't miss anything in the docs,
because it is just impossible to figure them out.
I have tried to follow the perl code to figure out
what is actually going on and it is too impenetrable
for me to understand
I have an application that uses the logger -t command to add specific
messages in /var/log/messages. I'd like to add those in a section of it's
own in the logwatch report but am having trouble following the information
in /usr/share/doc/logwatch-7.3 in the HOWTO doc.
I added my new script/filter
