Order of the machine-id files

[Fridrich Strba]

On 09/01/14 02:58, Yang Chengwei wrote:
> On Wed, Jan 08, 2014 at 09:12:35AM +0100, Fridrich Strba wrote: Is
> there any bugzilla used to track the issue?

https://bugzilla.novell.com/show_bug.cgi?id=857377

> Or at least you can open one on freedesktop.org for dbus upstream.

Will do, but I wanted to open it directly with a patch. I personally
don't like in my own projects bug reports that only add work, but love
those that directly fix the bug :)

> I think if it's the difference between /etc/machine-id and
> %localstatedir/lib/dbus/machine-id which cause problem, only change
> the read sequence isn't a real fix I think.

It seems that other libraries/frameworks use already the
/etc/machine-id directly and then have problem to communicate with dbus.

> For example, if A will fail because read
> %localstatedir/lib/dbus/machine-id first then B may fail because
> read /etc/machine-id first.

My (maybe wrong) assumption is that %localstatedir/lib/dbus/machine-id
would be used by dbus only directly. I would not expect other
applications using it directly.

> I think probably this is a distro issue,
> %localstatedir/lib/dbus/machine-id should be generated by
> dbus-uuidgen at first, then not bother on /etc/machine-id.

It is generated on SUSE, albeit, sometimes it happens that the
/etc/machine-id differs from that one. And since the rationale of the
/etc/machine-id seems to imply that that one will little by little
replace the dbus private, trying this solution.

> See tools/dbus-uuidgen.c also. Your patch does change the
> well-known behavior of dbus-uuidgen too.

Thanks, will have a look.

Cheers

Fridrich