Send connman mailing list submissions to connman@lists.01.org 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 connman-requ...@lists.01.org
You can reach the person managing the list at connman-ow...@lists.01.org When replying, please edit your Subject line so it is more specific than "Re: Contents of connman digest..." Today's Topics: 1. Does not create resolv.conf parent directories (Nuno Gon?alves) 2. Re: Does not create resolv.conf parent directories (Slava Monich) 3. Re: Does not create resolv.conf parent directories (Jonas Bonn) 4. Re: Does not create resolv.conf parent directories (Nuno Gon?alves) 5. Re: Does not create resolv.conf parent directories (Roy Reese) ---------------------------------------------------------------------- Message: 1 Date: Mon, 22 Oct 2018 15:43:40 +0200 From: Nuno Gon?alves <nuno...@gmail.com> To: connman@lists.01.org Subject: Does not create resolv.conf parent directories Message-ID: <caexmxlr5y3r1w-et-g6nb7hw41hok_x78ittdyghrlu6cvz...@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hi, Connman does not create the parent directories before attempting to create resolv.conf. As a result on boot, if /var/run/connman does not exist, this error message is printed: Cannot create /var/run/connman/resolv.conf falling back to /etc/resolv.conf I believe creating this directories, in temporary partitions, should be a responsibility of connman. Would like some confirmation because I submit a patch. Thanks, Nuno ------------------------------ Message: 2 Date: Mon, 22 Oct 2018 18:28:52 +0300 From: Slava Monich <slava.mon...@jolla.com> To: connman@lists.01.org Subject: Re: Does not create resolv.conf parent directories Message-ID: <73270e0e-9c08-7491-92b4-79a4e5f77...@jolla.com> Content-Type: text/plain; charset=utf-8; format=flowed Hi Nuno, > Hi, > > Connman does not create the parent directories before attempting to > create resolv.conf. > > As a result on boot, if /var/run/connman does not exist, this error > message is printed: > > Cannot create /var/run/connman/resolv.conf falling back to /etc/resolv.conf > > I believe creating this directories, in temporary partitions, should > be a responsibility of connman. As far as I understand it's supposed to be done by systemd-tmpfiles [1] based on generated config [2]. > Would like some confirmation because I submit a patch. > > Thanks, > Nuno Cheers, -Slava [1] https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html [2] https://git.kernel.org/pub/scm/network/connman/connman.git/tree/scripts/connman_resolvconf.conf.in ------------------------------ Message: 3 Date: Mon, 22 Oct 2018 17:34:19 +0200 From: Jonas Bonn <jo...@southpole.se> To: Slava Monich <slava.mon...@jolla.com>, connman@lists.01.org Subject: Re: Does not create resolv.conf parent directories Message-ID: <3fd15395-8dcd-2a4b-094d-ff1529620...@southpole.se> Content-Type: text/plain; charset=utf-8; format=flowed On 22/10/18 17:28, Slava Monich wrote: > Hi Nuno, > >> Hi, >> >> Connman does not create the parent directories before attempting to >> create resolv.conf. >> >> As a result on boot, if /var/run/connman does not exist, this error >> message is printed: >> >> Cannot create /var/run/connman/resolv.conf falling back to >> /etc/resolv.conf >> >> I believe creating this directories, in temporary partitions, should >> be a responsibility of connman. > > As far as I understand it's supposed to be done by systemd-tmpfiles [1] > based on generated config [2]. Even better would be to set RuntimeDirectory in the service file. That way all the private filesystem namespaces, dynamic user, etc. bits work automatically. The original question is relevant though if connman is started by something other than systemd, though. In that case it makes sense for connman to create the directory if it can. Do we still cater to users that don't run systemd? I wouldn't bother but I think that's still a controversial view... /Jonas > >> Would like some confirmation because I submit a patch. >> >> Thanks, >> Nuno > > Cheers, > -Slava > > [1] https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html > [2] > https://git.kernel.org/pub/scm/network/connman/connman.git/tree/scripts/connman_resolvconf.conf.in > > > _______________________________________________ > connman mailing list > connman@lists.01.org > https://lists.01.org/mailman/listinfo/connman ------------------------------ Message: 4 Date: Mon, 22 Oct 2018 17:36:28 +0200 From: Nuno Gon?alves <nuno...@gmail.com> To: slava.mon...@jolla.com Cc: connman@lists.01.org Subject: Re: Does not create resolv.conf parent directories Message-ID: <CAEXMXLTgc-Uh2OviY=1yhyfe2pi60veof-uyjwz+mwvngzu...@mail.gmail.com> Content-Type: text/plain; charset="UTF-8" I missed that tmpfiles.d requirement. Thanks for taking the time to point that. On Mon, Oct 22, 2018 at 5:28 PM Slava Monich <slava.mon...@jolla.com> wrote: > > Hi Nuno, > > > Hi, > > > > Connman does not create the parent directories before attempting to > > create resolv.conf. > > > > As a result on boot, if /var/run/connman does not exist, this error > > message is printed: > > > > Cannot create /var/run/connman/resolv.conf falling back to /etc/resolv.conf > > > > I believe creating this directories, in temporary partitions, should > > be a responsibility of connman. > > As far as I understand it's supposed to be done by systemd-tmpfiles [1] > based on generated config [2]. > > > Would like some confirmation because I submit a patch. > > > > Thanks, > > Nuno > > Cheers, > -Slava > > [1] https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html > [2] > https://git.kernel.org/pub/scm/network/connman/connman.git/tree/scripts/connman_resolvconf.conf.in ------------------------------ Message: 5 Date: Mon, 22 Oct 2018 19:24:26 +0200 From: "Roy Reese" <waterbeare...@gmx.com> To: connman@lists.01.org Subject: Re: Does not create resolv.conf parent directories Message-ID: <trinity-31648179-cc3a-4b76-9afc-ec6ae2b74755-1540229066259@3c-app-mailcom-bs11> Content-Type: text/plain; charset=UTF-8 > Enviar: lunes 22 de octubre de 2018 a las 17:34 > De: "Jonas Bonn" <jo...@southpole.se> > Para: "Slava Monich" <slava.mon...@jolla.com>, connman@lists.01.org > Asunto: Re: Does not create resolv.conf parent directories > > > > On 22/10/18 17:28, Slava Monich wrote: > > Hi Nuno, > > > >> Hi, > >> > >> Connman does not create the parent directories before attempting to > >> create resolv.conf. > >> > >> As a result on boot, if /var/run/connman does not exist, this error > >> message is printed: > >> > >> Cannot create /var/run/connman/resolv.conf falling back to > >> /etc/resolv.conf > >> > >> I believe creating this directories, in temporary partitions, should > >> be a responsibility of connman. > > > > As far as I understand it's supposed to be done by systemd-tmpfiles [1] > > based on generated config [2]. > > Even better would be to set RuntimeDirectory in the service file. That > way all the private filesystem namespaces, dynamic user, etc. bits work > automatically. > > The original question is relevant though if connman is started by > something other than systemd, though. In that case it makes sense for > connman to create the directory if it can. Do we still cater to users > that don't run systemd? I wouldn't bother but I think that's still a > controversial view... > > /Jonas > I would like to hear the answer to that. I use Enlightenment and like Connman, but have about had it with systemd. There are still good non-systemd distros (Gentoo, Slackware, MX Linux, and newer Artix) and I am increasingly inclined to switch out, especially to Artix which is Arch w/o systemd. > > > >> Would like some confirmation because I submit a patch. > >> > >> Thanks, > >> Nuno > > > > Cheers, > > -Slava > > > > [1] https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html > > [2] > > https://git.kernel.org/pub/scm/network/connman/connman.git/tree/scripts/connman_resolvconf.conf.in > > > > > > _______________________________________________ > > connman mailing list > > connman@lists.01.org > > https://lists.01.org/mailman/listinfo/connman > _______________________________________________ > connman mailing list > connman@lists.01.org > https://lists.01.org/mailman/listinfo/connman > ------------------------------ Subject: Digest Footer _______________________________________________ connman mailing list connman@lists.01.org https://lists.01.org/mailman/listinfo/connman ------------------------------ End of connman Digest, Vol 36, Issue 20 ***************************************