[Oisf-devel] Suricata startup

Steve Grubb sgrubb at redhat.com
Mon Feb 22 16:08:47 UTC 2010

On Monday 22 February 2010 10:39:17 am Will Metcalf wrote:
> > First question, as a daemon....isn't this way too verbose?
> Hmmm maybe I have seen quite a few daemons print out some sort of info
> before forking to a background process.  I will discuss this with the
> team.

If its something important, like the reason its not going to startup, that 
might be OK. But I would drop informational messages hitting the screen. If 
they are something an admin might need to research later, then perhaps it 
could hit syslog.
> > Why does the project's config file produce these warnings?
> Yes, we need to clean this up, we should not display warnings when we
> use the engine defaults.

Thanks. I suppose this is something that needs to be fixed in code or can the 
config file be arranged such that these do not come out?

> > Why did suricata fail to start up?
> Im interested to see what command line options you passed, as we
> should tell you what option you passed was invalid in getopt parsing,
> as this where this message is usually displayed.

-D -c /etc/suricata/suricata.yaml


More information about the Oisf-devel mailing list