2 .TH "SYSTEMD\&.SNAPSHOT" "5" "" "systemd 217" "systemd.snapshot"
3 .\" -----------------------------------------------------------------
4 .\" * Define some portability stuff
5 .\" -----------------------------------------------------------------
6 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7 .\" http://bugs.debian.org/507673
8 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
12 .\" -----------------------------------------------------------------
13 .\" * set default formatting
14 .\" -----------------------------------------------------------------
15 .\" disable hyphenation
17 .\" disable justification (adjust text to left margin only)
19 .\" -----------------------------------------------------------------
20 .\" * MAIN CONTENT STARTS HERE *
21 .\" -----------------------------------------------------------------
23 systemd.snapshot \- Snapshot unit configuration
26 \fIsnapshot\fR\&.snapshot
29 Snapshot units are not configured via unit configuration files\&. Nonetheless they are named similar to filenames\&. A unit whose name ends in
31 refers to a dynamic snapshot of the systemd runtime state\&.
33 Snapshots are not configured on disk but created dynamically via
34 \fBsystemctl snapshot\fR
37 for details) or an equivalent command\&. When created, they will automatically get dependencies 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
38 \fBsystemctl isolate\fR\&. They are useful to roll back to a defined state after temporarily starting/stopping services or similar\&.
43 \fBsystemd.unit\fR(5),
44 \fBsystemd.directives\fR(7)