File: nut-driver-enumerator-daemon-activator.service.in

package info (click to toggle)
nut 2.8.3-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 24,356 kB
  • sloc: ansic: 123,904; sh: 14,718; cpp: 12,558; makefile: 5,212; python: 1,114; perl: 855; xml: 47
file content (53 lines) | stat: -rw-r--r-- 2,454 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
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
# Network UPS Tools (NUT) systemd integration
# Copyright (C) 2011-2025 by NUT contributors
# Distributed under the terms of GPLv2+
# See https://networkupstools.org/
# and https://github.com/networkupstools/nut/

[Unit]
# This unit starts via nut-driver-enumerator-daemon-activator.path
# activation due to changes in ups.conf file, and triggers a reload
# of the nut-driver-enumerator-daemon.service so that one quickly
# re-processes the new configuration state.
# NOTE: This unit is intentionally not installed as PartOf/WantedBy
# anything, as it is only meant to be triggered by the path unit.
Description=Network UPS Tools - enumeration of configure-file devices into systemd unit instances (FS event-based activator for daemonized mode)
Conflicts=nut-driver-enumerator.service nut-driver-enumerator.path
After=local-fs.target
#Before=nut-driver.target
#PartOf=nut.target

Documentation=man:nut-driver-enumerator(@MAN_SECTION_CMD_SYS@)
Documentation=@NUT_WEBSITE_BASE@/docs/man/nut-driver-enumerator.html
Documentation=man:ups.conf(@MAN_SECTION_CFG@)
Documentation=@NUT_WEBSITE_BASE@/docs/man/ups.conf.html
Documentation=man:upsdrvsvcctl(@MAN_SECTION_CMD_SYS@)
Documentation=@NUT_WEBSITE_BASE@/docs/man/upsdrvsvcctl.html
Documentation=man:nut.conf(@MAN_SECTION_CFG@)
Documentation=@NUT_WEBSITE_BASE@/docs/man/nut.conf.html

[Service]
### Script needs privileges to restart units
#User=@RUN_AS_USER@
#Group=@RUN_AS_GROUP@
User=root
Type=oneshot
# Non-blocking systemd message posting should not take long,
# or should be aborted and retried if it does (system bugs)
TimeoutStartSec=10s
# If some process is writing the ups.conf file, it can be interpreted in
# some conditions by .path unit as many events requiring it to start -
# and eventually this gets throttled as a quickly started-restarted unit.
# While it should be permitted for manual start (likely .path trigger too)
# after interval expiration, this might race-condition to not detect some
# latest update into the configuration file if it happens after the main
# script loop has slurped intermediate state of device config.
# Note: Using the older but still supported Service/StartLimitInterval
# see https://lists.freedesktop.org/archives/systemd-devel/2017-July/039255.html
# for broader compatibility.
StartLimitInterval=0
ExecStart=/bin/systemctl reload-or-restart --no-block nut-driver-enumerator-daemon.service

[Install]
### No install, see comment above
#WantedBy=nut.target