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"
4 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
7 This file is part of systemd.
9 Copyright 2010 Lennart Poettering
11 systemd is free software; you can redistribute it and/or modify it
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
14 (at your option) any later version.
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
19 Lesser General Public License for more details.
21 You should have received a copy of the GNU Lesser General Public License
22 along with systemd; If not, see <http://www.gnu.org/licenses/>.
25 <refentry id="systemd.snapshot">
27 <title>systemd.snapshot</title>
28 <productname>systemd</productname>
32 <contrib>Developer</contrib>
33 <firstname>Lennart</firstname>
34 <surname>Poettering</surname>
35 <email>lennart@poettering.net</email>
41 <refentrytitle>systemd.snapshot</refentrytitle>
42 <manvolnum>5</manvolnum>
46 <refname>systemd.snapshot</refname>
47 <refpurpose>Snapshot unit configuration</refpurpose>
51 <para><filename><replaceable>snapshot</replaceable>.snapshot</filename></para>
55 <title>Description</title>
57 <para>Snapshot units are not configured via unit
58 configuration files. Nonetheless they are named
59 similar to filenames. A unit name whose name ends in
60 <filename>.snapshot</filename> refers to a dynamic
61 snapshot of the systemd runtime state.</para>
63 <para>Snapshots are not configured on disk but created
64 dynamically via <command>systemctl snapshot</command>
66 <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>
67 for details) or an equivalent command. When created,
68 they will automatically get dependencies on the
69 currently activated units. They act as saved
70 runtime state of the systemd manager. Later on, the
71 user may choose to return to the saved state via
72 <command>systemctl isolate</command>. They are
73 useful to roll back to a defined state after
74 temporarily starting/stopping services or
79 <title>See Also</title>
81 <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
82 <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
83 <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
84 <citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry>