At 18:31 10.04.2004, Tom Eastep wrote:
Tom Eastep wrote:
Stijn Jonker wrote:
It works fine here after a small modification in "firewall" on line 5757:
Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... /usr/share/shorewall/firewall: line 5757: [: missing `]'
firewall:5757 [ -n "$CONFIG_PATH"] || CONFIG_PATH=/etc/shorewall:/usr/share/shorewall changed it to: [ -n "$CONFIG_PATH" ] || CONFIG_PATH=/etc/shorewall:/usr/share/shorewall
Maybe it has to do with the version of sh/bash:
Just a plain ordinary bug -- thanks. I've updated CVS with the correction.
Now that this feature is implemented, I would like to re-open our earlier discussion about how the Shorewall LRP should be structured. As a starter, I would be happy to release the LRP's shorewall.conf file with a special CONFIG_PATH. I would think though that a change in the /var/lib/lrcfg/shorwall.conf file would also be in order so that the entries pointed to a directory that wasn't overwritten when a new Shorewall LRP was loaded. What is unclear to me is how this directory gets populated initially.
As I suggested some time ago could this be solved by falling back to the default shorewall.conf file if the file pointed to by CONFIG_PATH did not exist?
Erich
THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
