From 5b5fe82854fa70be22efb61386516801b5b95a95 Mon Sep 17 00:00:00 2001 From: Konrad Bucheli Date: Thu, 5 Sep 2024 08:11:48 +0200 Subject: [PATCH] remove systemd stuff --- .../puppet/components/systemd.rst | 77 ------------------- 1 file changed, 77 deletions(-) delete mode 100644 engineering-guide/puppet/components/systemd.rst diff --git a/engineering-guide/puppet/components/systemd.rst b/engineering-guide/puppet/components/systemd.rst deleted file mode 100644 index 44f41b26..00000000 --- a/engineering-guide/puppet/components/systemd.rst +++ /dev/null @@ -1,77 +0,0 @@ -``systemd`` -=========== - -This module provides defined types to create systemd units. It automatically -takes care of reloading systemd when necessary, automatically generates correct -names for ``.mount`` units, etc. - -The parameters of defined types are usually similar to the systemd option names -that they represent. Camel case (as used by systemd) is transformed to the -lowercase-with-underscore style usually used with Puppet, e.g. ``OnCalendar`` in -systemd becomes ``on_calendar``. - - -Parameters ----------- - -``default_target`` -~~~~~~~~~~~~~~~~~~ - -The systemd default target, i.e. usually one of ``multi-user.target`` or -``graphical.target``. - - -Defined Types -------------- - -All units support the following parameters for the ``[Unit]`` or ``[Install]`` -sections: - -- ``description`` -- ``wanted_by`` - - -``systemd::timer`` -~~~~~~~~~~~~~~~~~~ - -Creates a timer unit. - -Parameters: - -- ``on_calendar`` -- ``unit`` - - -``systemd::mount`` -~~~~~~~~~~~~~~~~~~ - -Creates a mount unit. The name of the unit file has to be (an encoded form of) -the mountpoint, which is automatically generated. See ``systemd.mount(5)`` for -details. - -Parameters: - -- ``what`` -- ``where`` -- ``options`` - - -``systemd.service`` -~~~~~~~~~~~~~~~~~~~ - -- ``type`` (default: ``simple``) -- ``exec_start`` - - -Examples --------- - -Defining a timer unit -~~~~~~~~~~~~~~~~~~~~~ - -Timer units integrate nicely with the remaining services. They can be managed -through ``systemctl(1)`` and their log messages can easily be accessed through -``journalctl -u xxxxx.timer``. - -A timer unit needs a corresponding service unit which executes the actual -command.