4ac0d30e4d
* This type of data is called metadata * Systemd config file - tested on Debian 9, you may have to adjust paths/uids if your deployment differs * Add collectd monitoring script * Only write PID after last fork - should fix systemd integration
19 lines
447 B
Desktop File
19 lines
447 B
Desktop File
[Unit]
|
|
Description=Bitmessage Daemon
|
|
After=network.target auditd.service
|
|
|
|
[Service]
|
|
ExecStart=/usr/bin/python2 /usr/src/PyBitmessage/src/bitmessagemain.py
|
|
ExecReload=/bin/kill -HUP $MAINPID
|
|
KillMode=process
|
|
Restart=on-failure
|
|
Type=forking
|
|
PIDFile=/var/lib/bitmessage/.config/PyBitmessage/singleton.lock
|
|
User=bitmessage
|
|
Group=nogroup
|
|
WorkingDirectory=/var/lib/bitmessage
|
|
Environment="HOME=/var/lib/bitmessage"
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|