Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: Connman very slow to reconnect after every warm reboot
(stef204)
----------------------------------------------------------------------
Message: 1
Date: Thu, 19 Apr 2018 09:42:21 -0600
From: stef204 <[email protected]>
To: Daniel Wagner <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: Connman very slow to reconnect after every warm reboot
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
19.04.2018, 01:01, "Daniel Wagner" <[email protected]>:
>
> Well, you could try the connman.service file a 3 releases ago to see if
> it makes a difference. The only real thing I see in the git history (3-4
> releases range) is
>
> fe10df64f3f0 ("connman.service: Start ConnMan after systemd-sysusers")
>
I have edited the service file and used an override on the
"After:systemd-sysusers" to remove it.
I used
# systemctl edit connman
to create a drop in override file which contains:
[Unit]
After=dbus.service network-pre.target
Is that correct of do I need to clear the After line first like this:
[Unit]
After=
After=dbus.service network-pre.targe
I rebooted a few times, and it does not seem to change anything.
If the above is correct, I will revert using #systemctl revert connman
And then try the log as you suggested:
# connmand -d 2>&1 | ts '[%H:%M:%.S]' | tee connman.log
>
>> ?Cannot create /var/run/connman/resolv.conf falling back to /etc/resolv.conf
>
> That might be a problem. Although then if ConnMan wouldn't not be able
> to setup the DNS resolver it would never work. Still check what happens
> with the resolv.conf. It is a global resource NetworkManager and also
> systemd-resolvd are trying to access. In the past ConnMan also just
> grapped the file. Just recently we teached ConnMan to behave more
> friendly and don't grab the file it all the time.
>
systemd-resolved is inactive on my box and I do not have NetworkManager
installed (only libnm required by some iso imaging program.)
> If that all failes try to create a log with timestamps. Maybe we can see
> then what takes so long:
>
> ?????connmand -d 2>&1 | ts '[%H:%M:%.S]' | tee connman.log
>
> I suppose you don't need the ts for journald since it has its own
> timestamp. In this case just start ConnMan with '-d' and look at the log
> file.
>
I'll disable the connman systemd service and then will try either "# connmand
-d 2>&1 | ts '[%H:%M:%.S]' | tee connman.log" or use "% journalctl -f" and "%
dmesg -w" to see what is gong on.
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 30, Issue 25
***************************************
