2020-04-23 22:07:36 +03:00
<?xml version='1.0'?>
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
2023-12-25 17:48:33 +03:00
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
2020-11-09 07:23:58 +03:00
<!-- SPDX - License - Identifier: LGPL - 2.1 - or - later -->
2020-04-23 22:07:36 +03:00
<refentry id= "sd_bus_get_name_machine_id" xmlns:xi= "http://www.w3.org/2001/XInclude" >
<refentryinfo >
<title > sd_bus_get_name_machine_id</title>
<productname > systemd</productname>
</refentryinfo>
<refmeta >
<refentrytitle > sd_bus_get_name_machine_id</refentrytitle>
<manvolnum > 3</manvolnum>
</refmeta>
<refnamediv >
<refname > sd_bus_get_name_machine_id</refname>
<refpurpose > Retrieve a bus client's machine identity</refpurpose>
</refnamediv>
<refsynopsisdiv >
<funcsynopsis >
<funcsynopsisinfo > #include < systemd/sd-bus.h> </funcsynopsisinfo>
<funcprototype >
<funcdef > int <function > sd_bus_get_name_machine_id</function> </funcdef>
<paramdef > sd_bus *<parameter > bus</parameter> </paramdef>
<paramdef > const char *<parameter > name</parameter> </paramdef>
<paramdef > sd_id128_t *<parameter > machine</parameter> </paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > <function > sd_bus_get_name_machine_id()</function> retrieves the D-Bus machine identity of the
machine that the bus client identified by <parameter > name</parameter> is running on. Internally, it calls
the <function > GetMachineId</function> method of the <constant > org.freedesktop.DBus.Peer</constant>
interface. The D-Bus machine identity is a 128-bit UUID. On Linux systems running systemd, this
corresponds to the contents of <filename > /etc/machine-id</filename> . On success, the machine identity is
stored in <parameter > machine</parameter> .</para>
</refsect1>
<refsect1 >
<title > Return Value</title>
<para > On success, this function returns a non-negative integer. On failure, it returns a negative
errno-style error code.</para>
<refsect2 >
<title > Errors</title>
<para > Returned errors may indicate the following problems:</para>
<variablelist >
<varlistentry >
<term > <constant > -EINVAL</constant> </term>
2024-04-18 03:45:51 +03:00
<listitem > <para > An argument is invalid.</para> </listitem>
2020-04-23 22:07:36 +03:00
</varlistentry>
<varlistentry >
<term > <constant > -ENOPKG</constant> </term>
2024-04-18 03:45:51 +03:00
<listitem > <para > The bus cannot be resolved.</para> </listitem>
2020-04-23 22:07:36 +03:00
</varlistentry>
<varlistentry >
<term > <constant > -ECHILD</constant> </term>
2024-04-18 03:45:51 +03:00
<listitem > <para > The bus was created in a different process, library or module instance.</para> </listitem>
2020-04-23 22:07:36 +03:00
</varlistentry>
<varlistentry >
<term > <constant > -ENOMEM</constant> </term>
2024-04-18 03:45:51 +03:00
<listitem > <para > Memory allocation failed.</para> </listitem>
2020-04-23 22:07:36 +03:00
</varlistentry>
</variablelist>
</refsect2>
</refsect1>
<xi:include href= "libsystemd-pkgconfig.xml" />
2023-09-04 15:46:35 +03:00
<refsect1 >
<title > History</title>
2024-04-18 03:45:51 +03:00
<para > <function > sd_bus_get_name_machine_id()</function> was added in version 221.</para>
2023-09-04 15:46:35 +03:00
</refsect1>
2020-04-23 22:07:36 +03:00
<refsect1 >
<title > See Also</title>
2023-12-22 21:09:32 +03:00
<para > <simplelist type= "inline" >
<member > <citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> </member>
<member > <citerefentry > <refentrytitle > sd-bus</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> </member>
</simplelist> </para>
2020-04-23 22:07:36 +03:00
</refsect1>
</refentry>