[Oisf-devel] Suricata startup

[Will Metcalf]

> 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.

> 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.

> 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.

As always Steve, thanks for your input.

Regards,

Will



On Mon, Feb 22, 2010 at 8:48 AM, Steve Grubb <sgrubb at redhat.com> wrote:
> Hello,
>
> I am starting suricata in daemon mode using the suricata.yaml file provided in
> the tarball and get this:
>
> Starting suricata: Warning: Invalid global_log_level assigned by user.
> Falling back on the default_log_level "Info"
> Warning: Invalid global_log_format supplied by user or format length exceeded
> limit of "128" characters.  Falling back on default log_format "[%i] %t - (%f:
> %l) <%d> (%n) -- "
> Warning: Output_interface not supplied by user.  Falling back on
> default_output_interface "Console"
> [27065] 22/2/2010 -- 09:43:32 - (suricata.c:567) <Info> (main) -- This is
> Suricata version 0.8.1
> [27065] 22/2/2010 -- 09:43:32 - (util-cpu.c:150) <Info> (UtilCpuPrintSummary)
> -- CPUs Summary:
> [27065] 22/2/2010 -- 09:43:32 - (util-cpu.c:152) <Info> (UtilCpuPrintSummary)
> -- CPUs online: 4
> [27065] 22/2/2010 -- 09:43:32 - (util-cpu.c:154) <Info> (UtilCpuPrintSummary)
> -- CPUs configured 4
> Suricata 0.8.1
> USAGE: suricata
> <snip>
>

>
> Thanks,
> -Steve
> _______________________________________________
> Oisf-devel mailing list
> Oisf-devel at openinfosecfoundation.org
> http://lists.openinfosecfoundation.org/mailman/listinfo/oisf-devel
>