File: systemd_integration.rst

package info (click to toggle)
autosuspend 9.0.1-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,196 kB
  • sloc: python: 5,431; xml: 13; makefile: 10; javascript: 1
file content (27 lines) | stat: -rw-r--r-- 1,170 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
.. _systemd-integration:

systemd integration
###################

Even though it is possible to run |project_program| manually (cf. :ref:`the manpage <man-command>`), in production use cases, the daemon will usually be run from `systemd`_.
For this purpose, the package ships with `service definition files <systemd service files>`_ for `systemd`_, so that you should be able to manage |project_program| via `systemd`_.
These files need to be installed in the appropriate locations for such service files, which depend on the Linux distribution.
Some common locations are:

* :file:`/usr/lib/systemd/system` (e.g. Archlinux packaged service files)
* :file:`/lib/systemd/system` (e.g. Debian packaged service files)
* :file:`/etc/systemd/system` (e.g. Archlinux manually added service files)

Binary installation packages for Linux distributions should have installed the service files at the appropriate locations already.

To start |project_program| via `systemd`_, execute:

.. code-block:: bash

   systemctl enable autosuspend.service

To start |project_program| automatically at system start, execute:

.. code-block:: bash

   systemctl start autosuspend.service