> This is AFTER init has been processed; why would your log fill up with > meaningless warnings? > My bad - I thought ipset warnings will always be shown. If warnings are not shown in case a given ipset exists *after* init has been processed, than I have no qualms with that approach at all - in fact, I like it. It should have been like that from the beginning. I am guessing, though, that the 'src' and 'dst' warnings aren't fixed yet, right?
>> You may be even more flexible and adopt a similar approach as openssh does: >> >> 1. Current directory >> 2. $HOME (if it exist) >> 3. /etc >> 4. /root >> 5. / >> 6. Environment variable >> > > I prefer this order with $HOME before /root since it allows my user id > to have a private Shorewall configuration unrelated to root's. I have, > in fact, already implemented that order :-) > I like that as well - it feels more "natural" that way somehow. >> Than I presume uninstall.sh was adapted accordingly to take full >> advantage of this, right? >> > > It has been. > Marvellous work! What do you want me to do with configure (if anything)? ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
