touch-packages team mailing list archive

[Simon McVittie <1508697@xxxxxxxxxxxxxxxxxx>]

That situation should never arise, because if the symlink exists, then
it was created by a successful boot with systemd sometime in the past;
systemd's API is that it guarantees to create /etc/machine-id before
running third-party code; and systemd never deletes the machine ID after
it has created one.

The ideal behaviour would be for dbus-uuidgen to replace the symlink
with a newly generated plain file, I think. I'd be happy to review a
patch (on freedesktop.org Bugzilla please) if that isn't already what it
does.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1508697

Title:
  dbus-uuidgen --ensure: Symlink instead of copy existing /etc/machine-
  id

Status in dbus package in Ubuntu:
  Triaged

Bug description:
  If you do a Wily desktop install, /var/lib/dbus/machine-id is a
  symlink to /etc/machine-id.

  If you do a Wily server install, /var/lib/dbus/machine-id is a file
  containing the same value as /etc/machine-id.

  Minor issue, but still a weird inconsistency between Ubuntu desktop
  and server.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1508697/+subscriptions