At 16:05 13.04.2004, you wrote:
Erich Titl wrote:
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?
Does it have to be populated? If Shorewall has a fallback set up which would be overridden by user configuration data then Shorewall would have a default configuration initially unless there is a user configuration file present. The shorewall.list would include the user configuration file but initially this file would be missing in the shorewall.lrp file. Loading a new release would thus not overwrite user configuration data. As soon as this configuration is saved then the newly created shorewall.lrp would contain the user configuration data valid at save time and therefore hold the complete configuration.
Is this feasible?
cheers 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
