Hi, so NM does enable the wait job by default also? Just timeout difference? If not I tend to agree that whatever the NM default is this one should have as well (assuming folks are happy with NM boot behaviour).
Let me know, - Alexander 2016-09-02 11:05 GMT+02:00 Kristian Klausen <klausenb...@hotmail.com>: > Never mind, maybe I should reread the bug report next time before I > respond.. > > > ________________________________ > From: klausenb...@hotmail.com > To: a...@debian.org; 827...@bugs.debian.org > CC: flor...@biree.name; cont...@bugs.debian.org > Subject: RE: Bug#827296: #827296 - connman: Connman slow down the boot when > no network available > Date: Fri, 2 Sep 2016 11:03:15 +0200 > > > Hello Alexander > > NetworkManager don't enable it as default which Connman does. > I think that is what the bug report is about :) > > Regards > Kristian Klausen > >> Subject: Bug#827296: #827296 - connman: Connman slow down the boot when no >> network available >> From: a...@debian.org >> Date: Fri, 2 Sep 2016 10:53:45 +0200 >> To: 827...@bugs.debian.org >> CC: flor...@biree.name; cont...@bugs.debian.org >> >> tags 827296 + moreinfo >> severity 827296 normal >> thanks >> >> Hi, >> >> this seems to be a feature. Seems you were able to resolve this issue? >> Anything you think that should be done here? >> >> Network Manager also has a similar wait job. timeout there is 30 >> seconds. connman just seem to have a higher default timeout in code >> (120 seconds). >> >> You could customize the job with --timeout=30 or we could use that as >> the default in the package if we feel there is strong reason to >> believe that majority of debian users will want the shorter timeout. >> >> Let me know if you are happy with the ability to tweak by yourself... >> >> Thanks, >> >> - Alexander >>
