Comment 71 for bug 64173

Alexander Sack wrote:

> For the patch ... its much appreciated, but making a user-defined
> variable out of this isn't the right way to go imo. In the end it
> would only help expert users, which is not what we want.

Well, changing a hardcoded value to some other hardcoded value isnt
exactly elegant, too. The patch creates the possibility to e.g. have an
"/etc/default/network-manager" file, store the timeout there and have it
set in the dbus startup script for network-manager.

That sure is a little more complicated but next time the timeout doesnt
fit the setup of someone, it will be as easy as starting a text editor
for them to have it fixed.

More so if you would place a hint in the not yet existing man-page for
network-manager (possibly along with some instructions on how to restart
network-manager properly because it tends to get stuck on some dbus
queue congestion issue after some quite large number of reconnects. I
really should file a bug on that and the missing manpage).

kind regards,
  Fionn