Hi,

On Tue, Nov 10, 2015 at 11:18:55AM -0500, Selva Nair wrote:
> On Mon, Nov 9, 2015 at 3:56 PM, Gert Doering <g...@greenie.muc.de> wrote:
> > On Mon, Nov 09, 2015 at 03:35:23PM -0500, Selva Nair wrote:
> >> Requires the installer to update the registry during an upgrade of exisitng
> >> installations, or notify the end user of the change in the default value of
> >> disconnect_on_suspend (0).
> >
> > What does this patch *do*?  Is this the "set up registry key on first
> > start" part (so we set the default differently now)?
> >
> > But that implies that an upgrade will not change the default, right?
> 
> On further thought, its better to go more bold on this. 
> Here is version 2 which culls the suspend processing.

I like the approach of "the installer changes the default, but if someone
*wants* this functionality, they can still enable it by changing the
(poorly documented, alas) registry key" better...

Leaving it in but having it disabled-by-default might be useful for 
different deployment scenarios than you have in mind.  It's there for
a reason, and much longer than the tap6 driver existed, so it fixed
other issues...  (like, "reconnect on a laptop after network change",
where you might need to wait for a --ping timeout otherwise)

gert

-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             g...@greenie.muc.de
fax: +49-89-35655025                        g...@net.informatik.tu-muenchen.de

Attachment: signature.asc
Description: PGP signature

Reply via email to