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. Connman unable to create /var/run/connman/resolv.conf (stef204)
2. Re: Connman unable to create /var/run/connman/resolv.conf
(KARBOWSKI Piotr)
3. Re: Connman unable to create /var/run/connman/resolv.conf
(stef204)
4. Re: Connman very slow to reconnect after every warm reboot
(stef204)
5. Re: Connman unable to create /var/run/connman/resolv.conf
(stef204)
----------------------------------------------------------------------
Message: 1
Date: Sun, 22 Apr 2018 04:55:47 -0600
From: stef204 <[email protected]>
To: connman <[email protected]>
Subject: Connman unable to create /var/run/connman/resolv.conf
Message-ID: <[email protected]>
Content-Type: text/plain
As a side note to my other thread/post, I notice that connman is unable to
create /var/run/connman/resolv.conf
It does not look possible to actually create the directory /var/run/connman
although /var/run/connman-vpn/ does exists.
On my box (and distro), /var/run is a symlink to /run
I (naively) tried to create /run/connman but obviously this got deleted upon
reboot and not recreated.
Connman falls back to /etc/resolv.conf which contains.... nothing.
% cat /etc/resolv/conf
# Generated by Connection Manager
Is the above expected? Or does it need fixing?
------------------------------
Message: 2
Date: Sun, 22 Apr 2018 13:26:24 +0200
From: KARBOWSKI Piotr <[email protected]>
To: [email protected]
Subject: Re: Connman unable to create /var/run/connman/resolv.conf
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi,
On 2018-04-22 12:55, stef204 wrote:
> As a side note to my other thread/post, I notice that connman is unable to
> create /var/run/connman/resolv.conf
>
> It does not look possible to actually create the directory /var/run/connman
> although /var/run/connman-vpn/ does exists.
>
> On my box (and distro), /var/run is a symlink to /run
>
> I (naively) tried to create /run/connman but obviously this got deleted upon
> reboot and not recreated.
>
> Connman falls back to /etc/resolv.conf which contains.... nothing.
>
> % cat /etc/resolv/conf
> # Generated by Connection Manager
>
> Is the above expected? Or does it need fixing?
By any chance you run Gentoo? There's a bug[1], where opentmpfiles, the
thing that is supposed to create this directory upon start, is not
auto-added into stage3 tarballs.
[1] https://bugs.gentoo.org/show_bug.cgi?id=649480
-- Piotr.
------------------------------
Message: 3
Date: Sun, 22 Apr 2018 05:59:54 -0600
From: stef204 <[email protected]>
To: KARBOWSKI Piotr <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: Connman unable to create /var/run/connman/resolv.conf
Message-ID: <[email protected]>
Content-Type: text/plain
22.04.2018, 05:26, "KARBOWSKI Piotr" <[email protected]>:
>
> By any chance you run Gentoo? There's a bug[1], where opentmpfiles, the
> thing that is supposed to create this directory upon start, is not
> auto-added into stage3 tarballs.
>
No, I run archlinux.
------------------------------
Message: 4
Date: Sun, 22 Apr 2018 06:42:18 -0600
From: stef204 <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: Connman very slow to reconnect after every warm reboot
Message-ID: <[email protected]>
Content-Type: text/plain
20.04.2018, 04:04, "stef204" <[email protected]>:
>
> I see one error besides the resolv.conf error above:
> connmand[5630]: Failed to set domainname to xxxx.box (this would be the
> domain name of my router)
>
For the record, I have fixed the above "secondary issue" by adding
CAP_SYS_ADMIN to the connman.service unit CapabilityBoundingSet line
I no longer get the " connmand[5630]: Failed to set domainname to xxxx.box "
error.
I am left with: the resolv.conf "issue" IF it is one, IOW cannot create
resolv.conf in /var/run/connman
Falling back to /etc/resolv.conf
But that file is empty--just contains this line:
# Generated by Connection Manager
AND left with the main issue I posted originally which is slow to (re)connect
to network after warm reboot.
I tried the git package (thinking there might be some updates in there which
might help resolve this but issue persists.)
------------------------------
Message: 5
Date: Sun, 22 Apr 2018 07:52:53 -0600
From: stef204 <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: Connman unable to create /var/run/connman/resolv.conf
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
22.04.2018, 05:26, "KARBOWSKI Piotr" <[email protected]>:
> Hi,
>
> On 2018-04-22 12:55, stef204 wrote:
>> ?As a side note to my other thread/post, I notice that connman is unable to
>> create /var/run/connman/resolv.conf
>>
>> ?It does not look possible to actually create the directory /var/run/connman
>> although /var/run/connman-vpn/ does exists.
>>
>> ?On my box (and distro), /var/run is a symlink to /run
>>
>> ?I (naively) tried to create /run/connman but obviously this got deleted
>> upon reboot and not recreated.
>>
>> ?Connman falls back to /etc/resolv.conf which contains.... nothing.
>>
>> ?% cat /etc/resolv/conf
>> ?# Generated by Connection Manager
>>
>> ?Is the above expected? Or does it need fixing?
>
> By any chance you run Gentoo? There's a bug[1], where opentmpfiles, the
> thing that is supposed to create this directory upon start, is not
> auto-added into stage3 tarballs.
>
> [1] https://bugs.gentoo.org/show_bug.cgi?id=649480
>
I seem to have now resolved this resolv.conf issue by adding in
/etc/systemd/system/connman.service.d/override.conf
[Service]
RuntimeDirectory=connman
Connman now can create the resolv.conf inside /var/run/connman
% cat /var/run/connman/resolv.conf
# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1
And I have symlinked /etc/resolv.conf to /var/run/connman/resolv.conf
I believe this resolv.conf problem is solved.
Now, back to the main issue of slow (re)connect unpon warm reboot. (I now
think this is kernel related.)
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 30, Issue 27
***************************************
