On Sun, 01.06.14 22:03, Mantas Mikulėnas (graw...@gmail.com) wrote:
On Sun, Jun 1, 2014 at 9:01 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Sat, 31.05.14 18:21, Rico Sagner (sag...@b1-systems.de) wrote:
Heya!
I think that the two ids would probably be better exposed by
On Mon, 02.06.14 13:31, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
On 01/06/14 20:03, Mantas Mikulėnas wrote:
Out of curiosity, wouldn't the existing
org.freedesktop.DBus.Peer.GetMachineId() work here?
In principle Peer.GetMachineId() returns the D-Bus machine ID
On 01/06/14 20:03, Mantas Mikulėnas wrote:
Out of curiosity, wouldn't the existing
org.freedesktop.DBus.Peer.GetMachineId() work here?
In principle Peer.GetMachineId() returns the D-Bus machine ID
/var/lib/dbus/machine-id, which in rare cases won't match the systemd
machine ID /etc/machine-id,
On Sat, 31.05.14 18:21, Rico Sagner (sag...@b1-systems.de) wrote:
Heya!
I think that the two ids would probably be better exposed by PID 1
istelf, instead of hostnamed. It's a bit difficult to come up with a
rule which props should be exposed from hostnamed and which ones from
PID1, but I think
On Sun, Jun 1, 2014 at 9:01 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Sat, 31.05.14 18:21, Rico Sagner (sag...@b1-systems.de) wrote:
Heya!
I think that the two ids would probably be better exposed by PID 1
istelf, instead of hostnamed. It's a bit difficult to come up with a
If hostnamectl is used with the --host option it does not
show the correct machine and boot IDs of the remote host.
The IDs are read by hostnamectl locally instead of querying
dbus on the remote host.
This patch makes systemd-hostnamed offer the IDs via dbus
and hostnamectl retrieve it this way.
