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?
Let say that for LEAF, the CONFIG_PATH is:
/etc/shorewalluser:/etc/shorewall:/usr/share/shorewall
Shorewall continues to release its configuration files into /etc/shorewall.
a) It seems like the entries in /var/lib/lrcfg/shorwall.conf need to point to /etc/shorewalluser.
b) Shorewall can't release files into /etc/shorewalluser because then a Shorewall upgrade will overwrite those files.
So how does /etc/shorewalluser get populated initially?
-Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED]
------------------------------------------------------- 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_id=1470&alloc_id=3638&op=click
_______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
