|Main Archive Page > Month Archives > snort-devel archives|
Glad to hear confirmation that it is only a documentation bug.
I am running as a daemon, and after a few other attempts to start snort I realized that other errors were only going to syslog, so I am no longer surprised this particular one was not printed to Stdout (after I sent the email here). (It's started now without `config pidpath`, so all is well.)
Thank you for your response, and I will try with the commandline option instead of the config directive for specifying the pid-path.
From: Steven Sturges [mailto:email@example.com] Sent: Monday, March 10, 2008 9:00 AM
To: Lee Clemens
Cc: firstname.lastname@example.org; 'Snort Developers Postings' Subject: Re: [Snort-devel] config pidpath directive no longer valid?
The config directive pidpath has been compiled out of the code for some time, at least since 2.6.1. We'll try to get the docs updated to reflect that.
However, it is supported on the commandline, you can use the --pid-path option and specify the path.
Depending on your other options (for example, if you daemonize, messages go to syslog). To test a configuration without daemonization, use -T on the commandline.
Lee Clemens wrote:
> Hello all,
> I am trying to run 184.108.40.206 with the following config directive defined in
> config pidpath: /applogs/snort/run
> But when starting Snort, I receive this in my syslogs:
> FATAL ERROR: Unknown config directive: config pidpath: /applogs/snort/run
> No errors are printed to STDOUT.
> I checked the snort_manual (v2.7.0 comes with the VRT rules released on
> 3-6-2008, by the way) and the config directive, pidpath, <i>is</i>
> explicitly defined in both the 2.7.0 and 2.8.0 Snort Manuals.
> Is this a documentation error, or is 220.127.116.11 no longer recognizing "config
> I can provide any system specific information if it would be useful.
> As a side note:
> I think it would be helpful if this fatal error was printed to
> STDOUT, instead of a FATAL ERROR <i>only</i> being printed to syslog.