Hi Gerald and Peter, I am CCing Peter maintaining insserv -- could you shine the light either it would be a reasonable approach worth pursuing?
LSB does not define virtual facility such as '$firewall'... some init scripts should assure that firewall is started before its own daemon, so fail2ban carries long but non-complete list of firewalls in its Should-* fields. Do you think it might be worth having all firewall packages providing "Provides:" 'firewall' boot facility (in addition to their own) so it could be used as a dependency in init scripts such as fail2ban. Thanks in advance for the feedback On Wed, 24 Nov 2010, Gerald Turner wrote: > Package: fail2ban > Version: 0.8.4-3 > Severity: wishlist > Hello, fail2ban has a long list of firewall software in the LSB headers of > it's > init script, it would be useful to have the package 'ferm' (an iptables > firewall setup package) added to the Should-Start/Stop > My /etc/insserv/overrides/fail2ban file looks like: > ### BEGIN INIT INFO > # Provides: fail2ban > # Required-Start: $local_fs $remote_fs > # Required-Stop: $local_fs $remote_fs > # Should-Start: $time $network $syslog iptables firehol shorewall ipmasq > arno-iptables-firewall ferm > # Should-Stop: $network $syslog iptables firehol shorewall ipmasq > arno-iptables-firewall ferm -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
