Summary: | On systemd systems, symlink dbus machine ID to /etc/machine-id | ||
---|---|---|---|
Product: | dbus | Reporter: | Simon McVittie <smcv> |
Component: | core | Assignee: | Simon McVittie <smcv> |
Status: | RESOLVED FIXED | QA Contact: | D-Bus Maintainers <dbus> |
Severity: | enhancement | ||
Priority: | medium | Keywords: | patch |
Version: | git master | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | review+ | ||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 101354 | ||
Attachments: |
Install a systemd tmpfiles.d snippet to create /var/lib/dbus/machine-id
Install a systemd tmpfiles.d snippet to create /var/lib/dbus/machine-id |
Description
Simon McVittie
2017-06-23 16:22:35 UTC
Comment on attachment 132166 [details] [review] Install a systemd tmpfiles.d snippet to create /var/lib/dbus/machine-id Review of attachment 132166 [details] [review]: ----------------------------------------------------------------- ::: bus/Makefile.am @@ +319,4 @@ > systemd-user/dbus.service.in \ > systemd-user/dbus.socket.in \ > sysusers.d/dbus.conf.in > + tmpfiles.d/dbus.conf.in This is clearly wrong - needs more backslashes. Created attachment 132263 [details] [review] Install a systemd tmpfiles.d snippet to create /var/lib/dbus/machine-id On systemd systems, /etc/machine-id is guaranteed to exist and has the same format as the D-Bus machine ID. The major D-Bus implementations read /etc/machine-id if it exists, but some less up-to-date implementations still only read /var/lib/dbus/machine-id. We can be nice to those implementations by ensuring /var/lib/dbus/machine-id is a symlink; this way, the two files can never get out of sync. --- Correct Makefile syntax Comment on attachment 132263 [details] [review] Install a systemd tmpfiles.d snippet to create /var/lib/dbus/machine-id Review of attachment 132263 [details] [review]: ----------------------------------------------------------------- r+ Thanks, fixed in git for 1.11.14. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.