2014-11-24 13:14:22 +03:00
<?xml version="1.0"?>
<!-- * - nxml - * -->
2019-03-14 16:40:58 +03:00
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2014-11-24 13:14:22 +03:00
<!--
2017-11-18 19:22:32 +03:00
SPDX-License-Identifier: LGPL-2.1+
2018-06-12 20:00:24 +03:00
Copyright © 2014 Didier Roche
2014-11-24 13:14:22 +03:00
-->
<refentry id= "systemd-machine-id-commit.service" >
2015-02-04 05:14:13 +03:00
<refentryinfo >
<title > systemd-machine-id-commit.service</title>
<productname > systemd</productname>
</refentryinfo>
<refmeta >
<refentrytitle > systemd-machine-id-commit.service</refentrytitle>
<manvolnum > 8</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd-machine-id-commit.service</refname>
2014-08-03 09:11:37 +04:00
<refpurpose > Commit a transient machine ID to disk</refpurpose>
2015-02-04 05:14:13 +03:00
</refnamediv>
<refsynopsisdiv >
<para > <filename > systemd-machine-id-commit.service</filename> </para>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
2015-09-23 20:36:21 +03:00
<para > <filename > systemd-machine-id-commit.service</filename> is an
2014-08-03 09:11:12 +04:00
early boot service responsible for committing transient
2015-09-23 20:36:21 +03:00
<filename > /etc/machine-id</filename> files to a writable disk file
2015-02-04 05:14:13 +03:00
system. See
<citerefentry > <refentrytitle > machine-id</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
2015-09-23 20:36:21 +03:00
for more information about machine IDs.</para>
<para > This service is started after
<filename > local-fs.target</filename> in case
<filename > /etc/machine-id</filename> is a mount point of its own
(usually from a memory file system such as
<literal > tmpfs</literal> ) and /etc is writable. The service will
invoke <command > systemd-machine-id-setup --commit</command> , which
writes the current transient machine ID to disk and unmount the
2015-02-04 05:14:13 +03:00
<filename > /etc/machine-id</filename> file in a race-free manner to
2015-09-23 20:36:21 +03:00
ensure that file is always valid and accessible for other
processes. See
<citerefentry > <refentrytitle > systemd-machine-id-setup</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
for details.</para>
<para > The main use case of this service are systems where
<filename > /etc/machine-id</filename> is read-only and initially
2014-08-03 09:11:12 +04:00
not initialized. In this case, the system manager will generate a
2015-09-23 20:36:21 +03:00
transient machine ID file on a memory file system, and mount it
over <filename > /etc/machine-id</filename> , during the early boot
phase. This service is then invoked in a later boot phase, as soon
as <filename > /etc</filename> has been remounted writable and the
ID may thus be committed to disk to make it permanent.</para>
2015-02-04 05:14:13 +03:00
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd-machine-id-setup</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > machine-id</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd-firstboot</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
</para>
</refsect1>
2014-11-24 13:14:22 +03:00
</refentry>