Hi >> I tested the above and error handling causes a problem... My desired >> outcome would be that it's possible to call "reenable" regardless of the >> current status of the interface. However, if it's already "disabled", >> then calling disable a second time causes a "startup_error" which bails >> us out before we call enable. >> >> Changing this seems to require a more invasive code change? Is this a >> direction you would be willing to consider? > Patch attached. > > -Tom
Splendid. I am using it against an old code base, but caveat light testing only, it seems to be fine. Note I didn't see it in the commit log in sourceforge yet? Confirming success here in the hope it will make the next release? Many thanks! Ed W ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
