Logwatch replacement..

[Ow Mun Heng]

On Sat, 2005-01-08 at 23:10, Harry Putnam wrote:
> Matthew Miller <mattdm at mattdm.org> writes:
> 
> > On Fri, Jan 07, 2005 at 02:33:11PM -0600, Harry Putnam wrote:
> >> Anyone here that can recommend a replacement for Logwatch that allows
> >> more fine grained user control over what gets reported?
> >
> > On my list of things to look at:
> >
> > <http://linux.duke.edu/projects/epylog/>
> 
> Thanks, yes that does look promising.  

> epylog (no args) 
> 
>   It fails with somekind of date format error from python:
> 
>   Invoking: "Initializing epylog"...
> Traceback (most recent call last):
>   File "/usr/sbin/epylog", line 300, in ?
>     main(sys.argv)
>   File "/usr/sbin/epylog", line 263, in main
>     epylog = Epylog(config_file, logger)
>   File "/usr/lib/python2.4/site-packages/epylog/__init__.py", line 227, in __init__
>     logtracker = LogTracker(config, logger)
>   File "/usr/lib/python2.4/site-packages/epylog/log.py", line 118, in __init__
>     self.monthmap = mkmonthmap()
>   File "/usr/lib/python2.4/site-packages/epylog/log.py", line 55, in mkmonthmap
>     months.append(time.strftime("%b", (0, i+1, 0, 0,
>  ValueError: day of month out of range
> 
> So I guess its not really ready for prime time yet.  The home page
> tells you that you must have python2.2 but Fedora is up to python2.4
> which may be the source of the problem.

I find that to be weird. I've ran it on multiple system w/ no problems.

FC2/FC3 and Gentoo too!

-- 
Ow Mun Heng
Gentoo/Linux on DELL D600 1.4Ghz 
98% Microsoft(tm) Free!! 
Neuromancer 14:37:16 up 5:29, 6 users, 
load average: 1.27, 1.51, 1.50