On Wed, May 04, 2005 at 09:56:18PM +0100, Jamie L. Penman-Smithson wrote:
> On Wed, 2005-05-04 at 19:44 +0200, maximilian attems wrote:
> > On Wed, 04 May 2005, Jamie L. Penman-Smithson wrote:
> > > > > Now logcheck doesn't usually allo for the @ in logs which results in
> > > > > bascially no igno
On Wed, 2005-05-04 at 19:44 +0200, maximilian attems wrote:
> On Wed, 04 May 2005, Jamie L. Penman-Smithson wrote:
> > > > Now logcheck doesn't usually allo for the @ in logs which results in
> > > > bascially no ignore line matching. Please add @ to the regexes, thanks.
> >
> > >
> > > ~/src/lo
On Wed, 04 May 2005, Jamie L. Penman-Smithson wrote:
> On Wed, 2005-05-04 at 00:12 +0200, maximilian attems wrote:
> > On Fri, 29 Apr 2005, Peter Palfrader wrote:
> > > Now logcheck doesn't usually allo for the @ in logs which results in
> > > bascially no ignore line matching. Please add @ to th
On Wed, 2005-05-04 at 00:12 +0200, maximilian attems wrote:
> On Fri, 29 Apr 2005, Peter Palfrader wrote:
> > Now logcheck doesn't usually allo for the @ in logs which results in
> > bascially no ignore line matching. Please add @ to the regexes, thanks.
>
> ~/src/logcheck/rulefiles/linux$ egrep
On Fri, 29 Apr 2005, Peter Palfrader wrote:
> When using with syslog-ng configured to also log the source of the log
> entry log lines look like:
>
> | Apr 24 06:47:01 [EMAIL PROTECTED] CRON[13878]: (pam_unix) session opened
> for user root by (uid=0)
>
> Now logcheck doesn't usually allo for t
5 matches
Mail list logo
