Thu Nov 23 16:36:19 EST 2017
the permissions to be able to access it.
Check that you do have a .conf file. Check where it is and check the
permissions on it.
If the file is there and you do have permissions, try "snort -c
/path/to/snort.conf" and see if Snort will start.
Always try to start snort manually. If you can start it manually and that
works, your problem isn't in the .conf or with snort. It would (usually)
be with whatever type of frontend you are using.
"When things get weird, the wierd turn pro." H.S. Thompson
More information about the Snort-users