thanks
As I've said in the documentation that mentions this init.d script, and the reason it is not installed in /etc/init.d by default, is that since there is no way to know what each administrator will name their firewall script there is no way to create a one-size-fits-all init.d script. That is left to the administrator to do with the caveat of expecting that an administrator working with firewall rules would be knowledgable to do that much on their own.
Regards,
Jeremy
On 8/20/06, Mihnea Capraru <[EMAIL PROTECTED]> wrote:
Package: fwbuilder
Version: 2.0.9
The init script supplied with this package
(/usr/share/doc/fwbuilder-common/examples/fwbuilder.init.d)
cannot start the firewall.
This happens because at line 14 it assumes:
SCRIPT="$SCRIPT_DIR/$(hostname -s).fw"
and this yields two problems.
Problem 1: on my machine, `hostname -s` returns 'localhost' instead
of 'example_name'.
Problem 2: this version of fwbuilder calls it's compiled
firewalls 'example_name Firewall.fw', not 'example_name.fw'
After fixing both problems, the firewall can be started. However detecting the
first one takes some minutes for advanced users, hours for beginners, and
forever for most people :).
Conclusion: a better way of detecting the script is needed.
--
Mihnea Capraru
