Bug#887343: systemd-timesyncd does not start with DynamicUser=yes

Michael Biebl biebl at debian.org
Tue Jan 16 06:41:23 GMT 2018


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 <fsateler at debian.org> 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 world
>> because systemd-timesync user won't exist if we are not running the service.
>> I'm not sure it makes sense anymore to support that usecase, so I have filed
>> the issue upstream.
> 
> This was fixed upstream:
> 
> https://github.com/systemd/systemd/commit/444c1915f94d7109b5fd97277b049ed17289848d

Thanks Felipe.

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?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180116/9cf16fee/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list