X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.snapshot.xml;fp=man%2Fsystemd.snapshot.xml;h=0000000000000000000000000000000000000000;hp=96069c324ae8e128e048b90cf931385fd1da22c3;hb=d3ad6bf3a64b4f13cb9a780c833e763afcff6085;hpb=140b399e33a9995b8bdb7afadf6aa08b632cb91b diff --git a/man/systemd.snapshot.xml b/man/systemd.snapshot.xml deleted file mode 100644 index 96069c324..000000000 --- a/man/systemd.snapshot.xml +++ /dev/null @@ -1,83 +0,0 @@ - - - - - - - - systemd.snapshot - systemd - - - - Developer - Lennart - Poettering - lennart@poettering.net - - - - - - systemd.snapshot - 5 - - - - systemd.snapshot - Snapshot unit configuration - - - - snapshot.snapshot - - - - Description - - Snapshot units are not configured via unit configuration - files. Nonetheless they are named similar to filenames. A unit - whose name ends in .snapshot refers to a - dynamic snapshot of the systemd runtime state. - - Snapshots are not configured on disk but created dynamically - via systemctl snapshot (see - systemctl1 - 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 - systemctl isolate. They are useful to roll back - to a defined state after temporarily starting/stopping services or - similar. - - - - See Also - - systemd1, - systemctl1, - systemd.unit5, - systemd.directives7 - - - -