Am 06.03.2017 um 14:03 schrieb Felipe Sateler:
> If this only affects PrivateTmp when /var is a symlink, I agree it is
> a corner case not worth spending much time on. My guess was that this
> would be a bug in a more common part of the code, and that it may
> affect other mount-related settings (RootDirectory=,
> WorkingDirectory=). I haven't been able to cause similar errors with
> those settings though.

Fwiw, I haven't tested other settings like RootDirectory.

What I noticed is that if /var is a symlink, services like
systemd-random-seed.service failed to start during boot.

I assume RequiresMountsFor=/var/lib/systemd/random-seed will not work
properly if /var is a symlink.

Using a bind mount I had a clean boot and shutdown (no failed services
or errors in the journal)


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

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Reply via email to