[Snort-devel] To printf or not to printf

tlewis at ...255... tlewis at ...255...
Mon Apr 29 16:57:02 EDT 2002

I prefer to write my own abstraction layer approximating syslog(3),
with types and/or severity as appropriate to the project.  Then you
can configure what level of verbosity you want and on which systems you
want it.  It's much easier to take a rich expression like that and
translate it into "Everything into stdout" than it is to take 10,000
"fprintf(stderr, ...)" statements and classify them.


Todd Lewis
tlewis at ...255...

"Bonsoir, Monet.  Work, work.  It is the most beautiful thing there is
       in the world."  -- Clemenceau

On Mon, 29 Apr 2002, Phil Wood wrote:

> Folks,
> This is about the chatty cathy syndrom which seems come and go.  By
> chatty cathy, I mean the various places in the code where reassuring messages
> are printed to either stderr or stdout.  I personally would like to see
> all messages directed to stderr, saving stdout for possibly piping output 
> to another process), at least when running in nids mode.  The problem
> is especially evident when people like myself redirect stderr to a file.
> I that case I get:
>   Rule application order:
> in my stderr file and
>  ->pass->activation->dynamic->alert->log->redalert
> to stdout.
> Drop me a line.  Or, does my mail go to /dev/null.
> Thanks,
> Phil
> _______________________________________________
> Snort-devel mailing list
> Snort-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/snort-devel

More information about the Snort-devel mailing list