[FS#3355] UMDNS: does not start on master with seccomp

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#3355 - UMDNS: does not start on master with seccomp 
User who did this - Kirill Elagin (kirelagin)

----------
Just a quick bump: this is still an issue in current snapshot.

I tried changing `defaultAction` to `SCMP_ACT_ALLOW` in `/etc/seccomp/umdns.json`, but this doesn’t seem to have any effect and I am still getting `Command failed: Request timed out` when trying to start the service` and `daemon.info procd: Instance umdns::instance1 s in a crash loop 7 crashes, 0 seconds since last crash` in the logs.

This makes me thing that the issue is not in the seccomp policy itself, but rather in the mechanism that `procd` uses to apply it.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=3355#comment9494

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.