You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Experiencing problems when firejail and transmission-daemon under systemd. The daemon is started from a systemd service file. Lots of messages like this are going in system log:
Feb 19 11:28:39 megat systemd[1]: transmission-daemon.service: Got notification message from PID 18737, but reception only permitted for main PID 18734
A partial solution was to include a further line in the transmission-daemon.service file "NotifyAccess=all"
Shutdown problem: Often (but not always), transmission-daemon will segfault and, whether it segfaults or not, the shutdown hangs for at least 90 seconds until some timeout mechanism finally kills all running processes.
The system runs a very vanilla installation running under KVM/QEMU, though I doubt if that’s relevant.
uname -a
Linux dl 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered:
From wordpress (user Robert in Basic Usage):
Experiencing problems when firejail and transmission-daemon under systemd. The daemon is started from a systemd service file. Lots of messages like this are going in system log:
Feb 19 11:28:39 megat systemd[1]: transmission-daemon.service: Got notification message from PID 18737, but reception only permitted for main PID 18734
A partial solution was to include a further line in the transmission-daemon.service file "NotifyAccess=all"
Shutdown problem: Often (but not always), transmission-daemon will segfault and, whether it segfaults or not, the shutdown hangs for at least 90 seconds until some timeout mechanism finally kills all running processes.
The system runs a very vanilla installation running under KVM/QEMU, though I doubt if that’s relevant.
uname -a
Linux dl 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: