[Bug 28906] Re: init script starts before NFS, NIS, DNS (need two stages)
I appreciate this is not a direct reference to firehol, but I have put together a patch for my fork, sanewall, see here: http://lists.sanewall.org/pipermail/sanewall-dev/2013-March/42.html If anyone is able to help test + verify the principle idea I can extend the change to cater for early NIS and DNS so that no special infrastructure to do multiple runs is needed. The patch can in theory be backported to firehol although it does depend on some earlier patches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/28906 Title: init script starts before NFS, NIS, DNS (need two stages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firehol/+bug/28906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253843] Re: don't quote log prefix
Is the reason is that the change (or similar) was already made upstream? See: http://firehol.cvs.sourceforge.net/viewvc/firehol/firehol/firehol.sh?r1=1.292r2=1.293 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/253843 Title: don't quote log prefix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firehol/+bug/253843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490317] Re: start script fails with upstart (if config requires DNS resolv)
At the risk of courting contreversy, is the real solution not to only use IP addresses in firehol scripts and possibly better failsafe if the firewall does not load (although good look googling for the reason or remotely logging into your box to fix it with everything set to deny). Using names means any resolution failure risks your firewall not starting up; the fact that DNS is apparently no longer resolving early enough in the boot process has simply exposed one cause. The fact is that when using a domain name IPs are resolved at load time and will be unchanged for the lifetime of the firewall - so it doesn't do what most people would really want anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/490317 Title: start script fails with upstart (if config requires DNS resolv) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
