Just few cents: 1. work around from austin DID work for me 2. Don't forget to change START_FIREHOL to YES in file /etc/default/firehol . It is not reported if it is set to NO, leaves you guessing what is going on. 3. shouldn't there be a "status" for /etc/init.d/firehol ? /sbin/firehol handles it !
-- firehol no longer starts on Feisty https://bugs.launchpad.net/bugs/78017 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
