From 36b4a7ba555540edb7648e0f97019280b4ac38de Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Sun, 8 Nov 2015 14:12:54 +0100 Subject: Remove snapshot unit type Snapshots were never useful or used for anything. Many systemd developers that I spoke to at systemd.conf2015, didn't even know they existed, so it is fairly safe to assume that this type can be deleted without harm. The fundamental problem with snapshots is that the state of the system is dynamic, devices come and go, users log in and out, timers fire... and restoring all units to some state from the past would "undo" those changes, which isn't really possible. Tested by creating a snapshot, running the new binary, and checking that the transition did not cause errors, and the snapshot is gone, and snapshots cannot be created anymore. New systemctl says: Unknown operation snapshot. Old systemctl says: Failed to create snapshot: Support for snapshots has been removed. IgnoreOnSnaphost settings are warned about and ignored: Support for option IgnoreOnSnapshot= has been removed and it is ignored http://lists.freedesktop.org/archives/systemd-devel/2015-November/034872.html --- man/systemctl.xml | 40 ----------------------- man/systemd.snapshot.xml | 83 ------------------------------------------------ man/systemd.unit.xml | 17 ++-------- man/systemd.xml | 6 ---- 4 files changed, 2 insertions(+), 144 deletions(-) delete mode 100644 man/systemd.snapshot.xml (limited to 'man') diff --git a/man/systemctl.xml b/man/systemctl.xml index 2fe24fd139..173c463d12 100644 --- a/man/systemctl.xml +++ b/man/systemctl.xml @@ -1341,46 +1341,6 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service - - Snapshot Commands - - - - snapshot NAME - - - Create a snapshot. If a snapshot name is specified, - the new snapshot will be named after it. If none is - specified, an automatic snapshot name is generated. In - either case, the snapshot name used is printed to standard - output, unless is specified. - - - A snapshot refers to a saved state of the systemd - manager. It is implemented itself as a unit that is - generated dynamically with this command and has dependencies - on all units active at the time. At a later time, the user - may return to this state by using the - isolate command on the snapshot unit. - - - Snapshots are only useful for saving and restoring - which units are running or are stopped, they do not - save/restore any other state. Snapshots are dynamic and lost - on reboot. - - - - delete PATTERN... - - - Remove a snapshot previously created with - snapshot. - - - - - Environment Commands diff --git a/man/systemd.snapshot.xml b/man/systemd.snapshot.xml deleted file mode 100644 index 96069c324a..0000000000 --- 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 - - - - diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 5c74318fec..caba7ea69d 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -60,7 +60,6 @@ target.target, path.path, timer.timer, - snapshot.snapshot, slice.slice, scope.scope @@ -90,7 +89,7 @@ swap file or partition, a start-up target, a watched file system path, a timer controlled and supervised by systemd1, - a temporary system state snapshot, a resource management slice or + a resource management slice or a group of externally created processes. The syntax is inspired by XDG @@ -115,8 +114,7 @@ systemd.target5, systemd.path5, systemd.timer5, - systemd.snapshot5. - systemd.slice5. + systemd.slice5, systemd.scope5. @@ -651,16 +649,6 @@ . - - IgnoreOnSnapshot= - - Takes a boolean argument. If - , this unit will not be included in - snapshots. Defaults to for device and - snapshot units, for the - others. - - StopWhenUnneeded= @@ -1431,7 +1419,6 @@ PrivateTmp=yes systemd.target5, systemd.path5, systemd.timer5, - systemd.snapshot5, systemd.scope5, systemd.slice5, systemd.time7, diff --git a/man/systemd.xml b/man/systemd.xml index 08ce99d0cc..6de18f8294 100644 --- a/man/systemd.xml +++ b/man/systemd.xml @@ -318,12 +318,6 @@ boot-up. See systemd.automount5. - Snapshot units can be used to temporarily save - the state of the set of systemd units, which later may be - restored by activating the saved snapshot unit. For more - information, see - systemd.snapshot5. - Timer units are useful for triggering activation of other units based on timers. You may find details in systemd.timer5. -- cgit v1.2.3-54-g00ecf