- <para>Snapshots are not configured on disk but created
- dynamically via <command>systemctl snapshot</command>
- (see
- <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
- 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
- <command>systemctl isolate</command>. They are
- useful to roll back to a defined state after
- temporarily starting/stopping services or
- similar.</para>
- </refsect1>
+ <para>Snapshots are not configured on disk but created dynamically
+ via <command>systemctl snapshot</command> (see
+ <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+ 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
+ <command>systemctl isolate</command>. They are useful to roll back
+ to a defined state after temporarily starting/stopping services or
+ similar.</para>
+ </refsect1>