From: Jason St. John Date: Sat, 15 Feb 2014 03:07:22 +0000 (-0500) Subject: man: use spaces instead of tabs X-Git-Tag: v209~126 X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=commitdiff_plain;h=b200a92cdc47b204e2ed7fbdd1eaf15abfd019c6 man: use spaces instead of tabs Several sections of the man pages included intermixed tabs and spaces; this commit replaces all tabs with spaces. --- diff --git a/man/crypttab.xml b/man/crypttab.xml index c563851f2..2d4150013 100644 --- a/man/crypttab.xml +++ b/man/crypttab.xml @@ -305,7 +305,7 @@ Use TrueCrypt in system encryption mode. This implies - tcrypt. + tcrypt. diff --git a/man/sd_bus_creds_get_pid.xml b/man/sd_bus_creds_get_pid.xml index d33533170..299c05a39 100644 --- a/man/sd_bus_creds_get_pid.xml +++ b/man/sd_bus_creds_get_pid.xml @@ -385,7 +385,7 @@ along with systemd; If not, see . Given field is not available in c. - + @@ -399,7 +399,7 @@ along with systemd; If not, see . sd_bus_get_owner_uid if the sender is not part of a systemd system unit, systemd user unit, systemd slice, logind session, or a systemd user session. - + diff --git a/man/systemd-delta.xml b/man/systemd-delta.xml index f802aa5eb..23fb8d1df 100644 --- a/man/systemd-delta.xml +++ b/man/systemd-delta.xml @@ -50,8 +50,8 @@ systemd-delta - OPTIONS - PREFIX/SUFFIX|SUFFIX + OPTIONS + PREFIX/SUFFIX|SUFFIX @@ -78,27 +78,27 @@ the name of the main configuration file, must match). For a fuller explanation, see systemd.unit5. - - - The command line argument will be split into a - prefix and a suffix. Either is optional. The prefix - must be one of the directories containing - configuration files (/etc, - /run, - /usr/lib, ...). If it is given, - only overriding files contained in this directory will - be shown. Otherwise, all overriding files will be - shown. The suffix must be a name of a subdirectory - containing configuration files like - tmpfiles.d, - sysctl.d or - systemd/system. If it is given, - only configuration files in this subdirectory (across - all configuration paths) will be analyzed. Otherwise, - all configuration files will be analyzed. If the - commandline argument is not given at all, all - configuration files will be analyzed. See below for - some examples. + + + The command line argument will be split into a + prefix and a suffix. Either is optional. The prefix + must be one of the directories containing + configuration files (/etc, + /run, + /usr/lib, ...). If it is given, + only overriding files contained in this directory will + be shown. Otherwise, all overriding files will be + shown. The suffix must be a name of a subdirectory + containing configuration files like + tmpfiles.d, + sysctl.d or + systemd/system. If it is given, + only configuration files in this subdirectory (across + all configuration paths) will be analyzed. Otherwise, + all configuration files will be analyzed. If the + commandline argument is not given at all, all + configuration files will be analyzed. See below for + some examples. @@ -200,21 +200,21 @@ - - Examples + + Examples - To see all local configuration: - systemd-delta + To see all local configuration: + systemd-delta - To see all runtime configuration: - systemd-delta /run + To see all runtime configuration: + systemd-delta /run - To see all system unit configuration changes: - systemd-delta systemd/system + To see all system unit configuration changes: + systemd-delta systemd/system - To see all runtime "drop-in" changes for system units: - systemd-delta --type=extended /run/systemd/system - + To see all runtime "drop-in" changes for system units: + systemd-delta --type=extended /run/systemd/system + Exit status diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 454cde4b4..8ad665643 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -751,29 +751,29 @@ ExecStart=/bin/echo $ONE $TWO ${TWO} be considered if the service does not implement a signal handler and exits as a direct result of receiving the signal. For example: - SuccessExitStatus=1 2 8 SIGKILL - ensures that exit codes 1, 2, 8 and - the termination signal - SIGKILL are - considered clean service terminations. - - - Note that if a process has a - signal handler installed and exits by - calling - _exit2 - in response to a signal, the - information about the signal is lost. - Programs should instead perform cleanup and kill themselves with the same signal instead. See - Proper handling of SIGINT/SIGQUIT — How to be a proper program. - - This option may appear more than once - in which case the list of successful - exit statuses is merged. If the empty - string is assigned to this option, the - list is reset, all prior assignments - of this option will have no - effect. + SuccessExitStatus=1 2 8 SIGKILL + ensures that exit codes 1, 2, 8 and + the termination signal + SIGKILL are + considered clean service terminations. + + + Note that if a process has a + signal handler installed and exits by + calling + _exit2 + in response to a signal, the + information about the signal is lost. + Programs should instead perform cleanup and kill themselves with the same signal instead. See + Proper handling of SIGINT/SIGQUIT — How to be a proper program. + + This option may appear more than once + in which case the list of successful + exit statuses is merged. If the empty + string is assigned to this option, the + list is reset, all prior assignments + of this option will have no + effect. diff --git a/man/systemd.socket.xml b/man/systemd.socket.xml index 6472750d0..71d1ab916 100644 --- a/man/systemd.socket.xml +++ b/man/systemd.socket.xml @@ -121,16 +121,16 @@ boot or late system shutdown should disable this option. - Socket units will have a - Before= dependency on the service - which they trigger added implicitly. No implicit - WantedBy= or - RequiredBy= dependency from the - socket to the service is added. This means that the - service may be started without the socket, in which - case it must be able to open sockets by itself. To - prevent this, an explicit Requires= - dependency may be added. + Socket units will have a + Before= dependency on the service + which they trigger added implicitly. No implicit + WantedBy= or + RequiredBy= dependency from the + socket to the service is added. This means that the + service may be started without the socket, in which + case it must be able to open sockets by itself. To + prevent this, an explicit Requires= + dependency may be added. Socket units may be used to implement on-demand starting of services, as well as parallelized starting