[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Logs-devel] why two options in rule?
From: |
Jim Prewett |
Subject: |
Re: [Logs-devel] why two options in rule? |
Date: |
Mon, 17 Apr 2006 07:35:21 -0600 (MDT) |
Hello,
match vs. no-match and delete vs. no-delete are inspired by Logsurfer.
I'm not really sure why the no- versions exist :) I have never found a
use for them in LoGS (they're somewhat useful in Logsurfer).
Maybe they should just be removed to simplify things?
Jim
James E. Prewett address@hidden address@hidden
Systems Team Leader LoGS: http://www.hpc.unm.edu/~download/LoGS/
Designated Security Officer OpenPGP key: pub 1024D/31816D93
HPC Systems Engineer III UNM HPC 505.277.8210
On Sun, 16 Apr 2006, Vijay Lakshminarayanan wrote:
> Hi all (Jim ;-),
>
> >From the manual:
>
> "In order to determine if a Message is matched by the Rule, the
> function stored in the "match" slot of the Rule must return non-nil
> and the function stored in the "no-match" slot must return nil when
> called with message as their argument."
>
> Why are there two options when creating a rule? Why not just have a
> "match" argument and likewise only one option for delete?
>
> ---
> Cheers
> Vijay
>
>
> _______________________________________________
> LoGS-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/logs-devel
>