Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

systemd/firejail interaction #1185

Closed
netblue30 opened this issue Mar 31, 2017 · 0 comments
Closed

systemd/firejail interaction #1185

netblue30 opened this issue Mar 31, 2017 · 0 comments
Labels
information_old (Deprecated; use "doc-todo" or "needinfo" instead) Information was/is required

Comments

@netblue30
Copy link
Owner

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

@netblue30 netblue30 added the information_old (Deprecated; use "doc-todo" or "needinfo" instead) Information was/is required label Mar 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
information_old (Deprecated; use "doc-todo" or "needinfo" instead) Information was/is required
Projects
None yet
Development

No branches or pull requests

1 participant