From 798d3a524ea57aaf40cb53858aaa45ec702f012d Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Tue, 3 Feb 2015 21:14:13 -0500 Subject: Reindent man pages to 2ch --- man/systemd-machine-id-commit.service.xml | 151 +++++++++++++++--------------- 1 file changed, 75 insertions(+), 76 deletions(-) (limited to 'man/systemd-machine-id-commit.service.xml') diff --git a/man/systemd-machine-id-commit.service.xml b/man/systemd-machine-id-commit.service.xml index c6a0e84564..7c8fc0874e 100644 --- a/man/systemd-machine-id-commit.service.xml +++ b/man/systemd-machine-id-commit.service.xml @@ -21,81 +21,80 @@ --> - - systemd-machine-id-commit.service - systemd - - - - Developer - Didier - Roche - didrocks@ubuntu.com - - - - - - systemd-machine-id-commit.service - 8 - - - - systemd-machine-id-commit.service - Commit transient machine-id to disk - - - - systemd-machine-id-commit.service - /usr/lib/systemd/systemd-machine-id-commit - - - - Description - - systemd-machine-id-commit.service is - a service responsible for committing any transient - /etc/machine-id file to a writable file - system. See - machine-id5 - for more information about this file. - - This service is started shortly after - local-fs.target if - /etc/machine-id is an independent mount - point (probably a tmpfs one) and /etc is writable. - systemd-machine-id-commit will then - write current machine ID to disk and unmount the transient - /etc/machine-id file in a race-free - manner to ensure that file is always valid for other - processes. - - Note that the traditional way to initialize the machine - ID in /etc/machine-id is to use - systemd-machine-id-setup by system - installer tools. You can also use - systemd-firstboot1 - to initialize the machine ID on mounted (but not - booted) system images. The main use case for that service is - /etc/machine-id being an empty file at - boot and initrd chaining to systemd giving it a read only file - system that will be turned read-write later during the boot - process. - - There is no consequence if that service fails other than - a newer machine-id will be generated during next system boot. - - - - - See Also - - systemd1, - systemd-machine-id-commit1, - systemd-machine-id-setup1, - machine-id5, - systemd-firstboot1 - - + + systemd-machine-id-commit.service + systemd + + + + Developer + Didier + Roche + didrocks@ubuntu.com + + + + + + systemd-machine-id-commit.service + 8 + + + + systemd-machine-id-commit.service + Commit transient machine-id to disk + + + + systemd-machine-id-commit.service + /usr/lib/systemd/systemd-machine-id-commit + + + + Description + + systemd-machine-id-commit.service is a + service responsible for committing any transient + /etc/machine-id file to a writable file + system. See + machine-id5 + for more information about this file. + + This service is started shortly after + local-fs.target if + /etc/machine-id is an independent mount point + (probably a tmpfs one) and /etc is writable. + systemd-machine-id-commit will then write + current machine ID to disk and unmount the transient + /etc/machine-id file in a race-free manner to + ensure that file is always valid for other processes. + + Note that the traditional way to initialize the machine ID + in /etc/machine-id is to use + systemd-machine-id-setup by system installer + tools. You can also use + systemd-firstboot1 + to initialize the machine ID on mounted (but not booted) system + images. The main use case for that service is + /etc/machine-id being an empty file at boot + and initrd chaining to systemd giving it a read only file system + that will be turned read-write later during the boot + process. + + There is no consequence if that service fails other than a + newer machine-id will be generated during next system boot. + + + + + See Also + + systemd1, + systemd-machine-id-commit1, + systemd-machine-id-setup1, + machine-id5, + systemd-firstboot1 + + -- cgit v1.2.3-54-g00ecf