On Tue, 2011-12-13 at 06:48 +0800, Antonio Borneo wrote: > > Or should we just leave it with a hard-coded 'vpnc' and not worry about > > it? > > The only issue I see in this case is for an hypothetical user that > runs vpnc and openconnect at same time on this "very" old version of > Suse. > The first SW to run will create a backup. The second, using same > service name, will just change "/etc/resolv.conf" since its action is > considered as an incremental change to "/etc/resolv.conf" made by same > service. > Can we accept this risk? I think so. I don't think *anything* is going to work particularly well if you join more than one VPN using vpnc-script, and then disconnect from them in anything but strictly the reverse of the order that you connected. I've committed and pushed your patch; thanks. -- dwmw2 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5818 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20111212/b27347e1/attachment-0001.bin>
