Michael Biebl [2018-01-16 7:41 +0100]:
> Even with this fix though, we should imho make sure to have
> libnss-systemd installed by default.
> See the problem with Recommends and the initial bootstrap I mentioned
> earlier.
> What are we going to do about this?
Hmm, in Debian I don't think we have
Am 15.01.2018 um 23:58 schrieb Felipe Sateler:
> Control: tags -1 patch fixed-upstream
>
> On Mon, Jan 15, 2018 at 10:42 AM, Felipe Sateler wrote:
>> It appears timesyncd wants to do this to support being run as root and then
>> dropping privileges. However, this will fail in the DynamicUser=yes
Control: tags -1 patch fixed-upstream
On Mon, Jan 15, 2018 at 10:42 AM, Felipe Sateler wrote:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/7883
>
> On Mon, Jan 15, 2018 at 8:57 AM, Martin Pitt wrote:
>>
>> Guido Günther [2018-01-15 12:14 +0100]:
>> > > > This seems to be cau
Control: forwarded -1 https://github.com/systemd/systemd/issues/7883
On Mon, Jan 15, 2018 at 8:57 AM, Martin Pitt wrote:
> Guido Günther [2018-01-15 12:14 +0100]:
> > > > This seems to be caused by the fact that libnss-systemd is not a hard
> > > > dependency of systemd. I'm not sure what the be
Am 15.01.2018 um 12:57 schrieb Martin Pitt:
> Note that *in general*, DynamicUser=yes does not *require* libnss-systemd.
> Services start without it, the only effect is that showing the process with
> tools like "ps" will not be able to resolve a dynamic user ID to a name - it
> will just be shown
Am 15.01.2018 um 12:57 schrieb Martin Pitt:
> If timesyncd in particular somehow wants to resolve the systemd-timesyncd
> system user in its own code, then that either should be fixed, or systemd
> needs
> to raise libnss-systemd to a Depends: for that particular bug/reason.
grepping through the
Guido Günther [2018-01-15 12:14 +0100]:
> > > This seems to be caused by the fact that libnss-systemd is not a hard
> > > dependency of systemd. I'm not sure what the best solution is? Having a
> > > service that is enabled by fails to start looks weird though. Maybe
> > > providing a static user i
Am 15.01.2018 um 12:55 schrieb Guido Günther:
> Turning it into a dependency would probably be best. It might be
> sufficient to have it as a dependency of systemd-sysv, not systemd
> itself.
Yes, the Recommends: libnss-systemd in systemd-sysv would be bumped to
Depends: libnss-systemd.
While th
Hi Michael,
On Mon, Jan 15, 2018 at 12:44:34PM +0100, Michael Biebl wrote:
> Hi Guido
>
> Am 15.01.2018 um 12:14 schrieb Guido Günther:
> > Hi,
> > On Mon, Jan 15, 2018 at 11:24:33AM +0100, Michael Biebl wrote:
> >> Am 15.01.2018 um 10:18 schrieb Guido Günther:
>
> >> It requires libnss-systemd,
Hi Guido
Am 15.01.2018 um 12:14 schrieb Guido Günther:
> Hi,
> On Mon, Jan 15, 2018 at 11:24:33AM +0100, Michael Biebl wrote:
>> Am 15.01.2018 um 10:18 schrieb Guido Günther:
>> It requires libnss-systemd, yes. Do you not have it installed?
>> It's a recommends, so should be installed by default
Hi,
On Mon, Jan 15, 2018 at 11:24:33AM +0100, Michael Biebl wrote:
> Am 15.01.2018 um 10:18 schrieb Guido Günther:
> > Package: systemd
> > Version: 236-3
> > Severity: normal
> > File: systemd-timesyncd.service
> >
> > Hi,
> > on a newly installed (without installing recommends) system¹
> > syst
Am 15.01.2018 um 10:18 schrieb Guido Günther:
> Package: systemd
> Version: 236-3
> Severity: normal
> File: systemd-timesyncd.service
>
> Hi,
> on a newly installed (without installing recommends) system¹
> systemd-timesyncd fails to start like
>
> $ systemctl status systemd-timesyncd
> ● syst
Package: systemd
Version: 236-3
Severity: normal
File: systemd-timesyncd.service
Hi,
on a newly installed (without installing recommends) system¹ systemd-timesyncd
fails to start like
$ systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
Loaded: load
13 matches
Mail list logo
