Hi On Fri, Jun 26, 2020 at 9:23 PM Lennart Poettering <lenn...@poettering.net> wrote: > You might need a newer libseccomp so that the syscall is actually > known by it. openat2 is a very recent syscall addition, and you need > to update libseccomp in lockstep if you want it to grok it.
Thanks for the details, I'll look into it. Anyway, is there any specific reason for not providing an option to disable seccomp (or make seccomp opt-in instead of default)? Thanks, Mohan R _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
