2009/1/24 <prosoluti...@gmx.net>: > I also want to point out one more thing that absolutely blows my mind: in > /etc/default/snort is a line: > > PARAMS="-m 027 -D -d " > Is this correct? Why are the daemon parameters in this file?
Yes. It is correct and, actually, standard in Debian packages. Take a look at /etc/default/exim4 or /etc/default/ntp, for example. In order to prevent users from modifying the init.d scripts directly only for parameter tweaking (which would produce issues when upgrading packages and the init.d changes) the parameters are moved over to a /etc/default file > Getting back to /etc/snort/snort.debian.conf, I read Javier's advice to one > user in a bug >response regarding the ALLOW_UNAVAILABLE option mentioned > earlier, that the user should >not edit snort.debian.conf manually? What is > this file doing there at all then? This totally does >not make sense. > Aren't there Debian policy guidelines against this kind of thing? Can a > >maintainer totally mince a package like this to the point where it doesn't > make sense? /etc/snort/snort.debian.conf, just like many other configuration files, is handled by Debian's configuration management system Debconf. In order to vary those contents you are supposed, as explained in the file, to run "dpkg-reconfigure snort" This certainly looks like a problem in your debconf priority settings. You are probably running your debconf settings in a 'high' value. What value have you set there? If your default value is 'high' (certainly, not a recommended setting) then run 'dpkg-reconfigure -pmedium snort'. (or -plow) The debconf prompts will guide you on how to configure Snort to have it up and running in no time. Regards Javier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
