On 3/8/19, KatolaZ <[email protected]> wrote: > > Then we could probably just ignore it, right? It turns out I was > making confusion between /etc/machine-id and > /car/lib/dbus/machine-id. There is no /etc/machine-id in any of my > machines, either on ascii or on beowulf, and I had forgotten you had > pushed the patch to elogind to use the dbus machine-id instead. > > We should just double-check that the dbus machine-id is regenerated at > reboot, as expected. >
There's no /etc/machine-id in my beowulf that was an upgrade from refracta ascii or in the beowulf live iso that I just made with live-sdk. Refractasnapshot excludes /var/lib/dbus/machine-id and blanks /etc/machine-id if it's present. Refractainstaller excludes /var/lib/dbus/machine-id and does nothing with /etc/machine-id. Isos made with live-sdk will have /var/lib/dbus/machine-id, and it's the same number every boot unless we remove the file. I just added 'rm -f /var/lib/dbus/machine-id' to blend_finalize() and now the iso has a different machine-id on every boot. If /etc/machine-id is missing, systemd-journald will fail. If the file is empty, it'll get a new number. (That doesn't concern us, but there's code for it in refractasnapshot because people use that on debian with systemd.) fsmithred _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
