Erich Titl wrote:
Tom

At 18:02 13.04.2004, Tom Eastep wrote:

Erich Titl wrote:

Does it have to be populated?


I think so if the /var/lib/lrpkg/shorwall.conf file points to it.


It could just use it if it exists (and makes sense).....

My point is that /var/lib/lrpkg/shorwall.conf should not point to files that do not exist.



I think that Charles's suggestion about using two packages makes this a bit more friendly. The main problem that I see with that approach is that it doesn't allow any way for me to add a new config file in the future and have it reflected in the Shorewall configuration menu.


Well, I believe they are not necessarily mutually exclusive.

If we include let's say /etc/shorewalluser/* in /var/lib/lrpkg/shorewall.list and /etc/shorewalluser/shorewall.conf in the /var/lib/lrpkg/swconf.list then, if swconf.lrp _was_ installed, the user configuration would be saved to swconf.lrp, else it would be saved to shorewall.lrp. In any case you would not need to populate /etc/shorewalluser/shorewall.conf as the backup script would take care of user config data. This sounds complicated, but from a user's perspective would be almost invisible.

Well, it sounds complicated to me -- I'm lost :-)



The main point I would like to see is a fallback configuration file which would be used if the user configuration is missing or produces a failure, so shorewall does not abort completely.



I assume that by "configuration file" you mean shorewall.conf (as opposed to shorwall.conf in /var/lib/lrpkg/).


-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

Reply via email to