blob: 291f16178ef0c7657cea34ac1b98d81cee0a3bfb [file] [log] [blame]
Tomas Cejkac95271a2016-03-02 09:07:19 +01001# It's not recommended to modify this file in-place, because it will be
2# overwritten during package upgrades. If you want to customize, the best
3# way is to create a file "/etc/systemd/system/netopeerguid.service",
4# containing
5# .include /lib/systemd/system/netopeerguid.service
6# ...make your changes here...
7# For more info about custom unit files, see
8# http://fedoraproject.org/wiki/Systemd#How_do_I_customize_a_unit_file.2F_add_a_custom_unit_file.3F
9#
10# For example, to pass additional options (for instance, -D definitions) to the
11# supervisor binary at startup, you need to create a file named
12# "/etc/systemd/system/netopeerguid.service" containing:
13# .include /lib/systemd/system/netopeerguid.service
14# [Service]
15# Environment=OPTIONS=-DMY_DEFINE
16
17[Unit]
18Description=NetopeerGUI backend daemon
19After=network.target local-fs.target remote-fs.target
20
21[Service]
22Type=simple
23Environment=LANG=C
Tomas Cejka18e505a2016-03-14 09:43:46 -040024ExecStart=@absbindir@/netopeerguid
Tomas Cejkac95271a2016-03-02 09:07:19 +010025KillMode=process
26PrivateTmp=false
27
28[Install]
29WantedBy=multi-user.target