[Pkg-systemd-maintainers] Bug#619244: Bug#619244: Bug#619244: systemd: unowned files after purge (policy 6.8, 10.8): /etc/machine-id

Simon McVittie smcv at debian.org
Tue Apr 15 13:25:44 BST 2014


On 15/04/14 13:10, Tobias Frost wrote:
> Maybe it is sufficient to agree on a load order, like switch the order dbus
> tries to read the uuid?

If there is a conflict, I consider consistency with dbus-from-the-past
to be a higher priority than with systemd. Of course, if all goes well,
there shouldn't be a conflict - if both files exist then they should
have the same contents.

The failure mode, if different components see different machine IDs, is
that a component might think another component is running remotely.
That's not *so* bad.

> But as systemd is supposed to start earlier, I guess, it is
> probably better to have dbus read it first to avoid races)

What matters is the order in which their postinsts created the machine
IDs. I believe d-i still installs sysvinit as pid 1, and wheezy d-i
certainly does, so it seems reasonably likely that the sort of systems
where this question is relevant will install dbus (as a dependency for
task-desktop, for instance) before systemd. In that case, everything is
fine, because systemd copies dbus' idea of the machine ID.

The failing case is when dbus is installed second, and generates an
entirely new machine ID instead of copying systemd's. As I said, I'd be
happy to review a patch.

    S




More information about the Pkg-systemd-maintainers mailing list