]>
Commit | Line | Data |
---|---|---|
b2c20dd9 LP |
1 | <?xml version='1.0'?> <!--*-nxml-*--> |
2 | <?xml-stylesheet type="text/xsl" href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"?> | |
3 | <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" | |
798d3a52 | 4 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> |
b2c20dd9 LP |
5 | |
6 | <!-- | |
7 | This file is part of systemd. | |
8 | ||
9 | Copyright 2010 Lennart Poettering | |
10 | ||
11 | systemd is free software; you can redistribute it and/or modify it | |
5430f7f2 LP |
12 | under the terms of the GNU Lesser General Public License as published by |
13 | the Free Software Foundation; either version 2.1 of the License, or | |
b2c20dd9 LP |
14 | (at your option) any later version. |
15 | ||
16 | systemd is distributed in the hope that it will be useful, but | |
17 | WITHOUT ANY WARRANTY; without even the implied warranty of | |
18 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU | |
5430f7f2 | 19 | Lesser General Public License for more details. |
b2c20dd9 | 20 | |
5430f7f2 | 21 | You should have received a copy of the GNU Lesser General Public License |
b2c20dd9 LP |
22 | along with systemd; If not, see <http://www.gnu.org/licenses/>. |
23 | --> | |
24 | ||
25 | <refentry id="systemd.snapshot"> | |
798d3a52 ZJS |
26 | <refentryinfo> |
27 | <title>systemd.snapshot</title> | |
28 | <productname>systemd</productname> | |
b2c20dd9 | 29 | |
798d3a52 ZJS |
30 | <authorgroup> |
31 | <author> | |
32 | <contrib>Developer</contrib> | |
33 | <firstname>Lennart</firstname> | |
34 | <surname>Poettering</surname> | |
35 | <email>lennart@poettering.net</email> | |
36 | </author> | |
37 | </authorgroup> | |
38 | </refentryinfo> | |
b2c20dd9 | 39 | |
798d3a52 ZJS |
40 | <refmeta> |
41 | <refentrytitle>systemd.snapshot</refentrytitle> | |
42 | <manvolnum>5</manvolnum> | |
43 | </refmeta> | |
b2c20dd9 | 44 | |
798d3a52 ZJS |
45 | <refnamediv> |
46 | <refname>systemd.snapshot</refname> | |
47 | <refpurpose>Snapshot unit configuration</refpurpose> | |
48 | </refnamediv> | |
b2c20dd9 | 49 | |
798d3a52 ZJS |
50 | <refsynopsisdiv> |
51 | <para><filename><replaceable>snapshot</replaceable>.snapshot</filename></para> | |
52 | </refsynopsisdiv> | |
b2c20dd9 | 53 | |
798d3a52 ZJS |
54 | <refsect1> |
55 | <title>Description</title> | |
b2c20dd9 | 56 | |
798d3a52 ZJS |
57 | <para>Snapshot units are not configured via unit configuration |
58 | files. Nonetheless they are named similar to filenames. A unit | |
59 | whose name ends in <literal>.snapshot</literal> refers to a | |
60 | dynamic snapshot of the systemd runtime state.</para> | |
b2c20dd9 | 61 | |
798d3a52 ZJS |
62 | <para>Snapshots are not configured on disk but created dynamically |
63 | via <command>systemctl snapshot</command> (see | |
64 | <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry> | |
65 | for details) or an equivalent command. When created, they will | |
66 | automatically get dependencies on the currently activated units. | |
67 | They act as saved runtime state of the systemd manager. Later on, | |
68 | the user may choose to return to the saved state via | |
69 | <command>systemctl isolate</command>. They are useful to roll back | |
70 | to a defined state after temporarily starting/stopping services or | |
71 | similar.</para> | |
72 | </refsect1> | |
b2c20dd9 | 73 | |
798d3a52 ZJS |
74 | <refsect1> |
75 | <title>See Also</title> | |
76 | <para> | |
77 | <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
78 | <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
79 | <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
80 | <citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry> | |
81 | </para> | |
82 | </refsect1> | |
b2c20dd9 LP |
83 | |
84 | </refentry> |