chiark / gitweb /
build-sys: make PolicyKit support compile-time optional (was runtime-optional already)
[elogind.git] / man / systemd.snapshot.xml
index 5e73cc6f789ef0e9e0ca7fd3d5a160450313001a..f7688e999829a0860c4451bc96183986c2248f4e 100644 (file)
@@ -9,16 +9,16 @@
   Copyright 2010 Lennart Poettering
 
   systemd is free software; you can redistribute it and/or modify it
-  under the terms of the GNU General Public License as published by
-  the Free Software Foundation; either version 2 of the License, or
+  under the terms of the GNU Lesser General Public License as published by
+  the Free Software Foundation; either version 2.1 of the License, or
   (at your option) any later version.
 
   systemd is distributed in the hope that it will be useful, but
   WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
-  General Public License for more details.
+  Lesser General Public License for more details.
 
-  You should have received a copy of the GNU General Public License
+  You should have received a copy of the GNU Lesser General Public License
   along with systemd; If not, see <http://www.gnu.org/licenses/>.
 -->
 
@@ -44,7 +44,7 @@
 
         <refnamediv>
                 <refname>systemd.snapshot</refname>
-                <refpurpose>systemd snapshot units</refpurpose>
+                <refpurpose>Snapshot unit configuration</refpurpose>
         </refnamediv>
 
         <refsynopsisdiv>
                 dynamically via <command>systemctl snapshot</command>
                 (see
                 <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-                for details) or an equivalent command. When created
+                for details) or an equivalent command. When created,
                 they will automatically get dependencies on the
-                currently activated units. They hence act as saved
-                runtime state of the systemd manager. Later on the
+                currently activated units. They act as saved
+                runtime state of the systemd manager. Later on, the
                 user may choose to return to the saved state via
-                <command>systemctl isolate</command>. They are hence
+                <command>systemctl isolate</command>. They are
                 useful to roll back to a defined state after
                 temporarily starting/stopping services or
                 similar.</para>
         <refsect1>
                   <title>See Also</title>
                   <para>
-                          <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
+                          <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
                           <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
-                          <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
+                          <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
+                          <citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry>
                   </para>
         </refsect1>