Remove flags from seccomp

It's not needed to expose those flags to the user.

Signed-off-by: Mauricio Vásquez <[email protected]>

Author: mauriciovasquezbernal

config-linux.md

@@ -624,15 +624,13 @@ The following parameters can be specified to set up seccomp:
     * `SECCOMP_FILTER_FLAG_TSYNC`
     * `SECCOMP_FILTER_FLAG_LOG`
     * `SECCOMP_FILTER_FLAG_SPEC_ALLOW`
-    * `SECCOMP_FILTER_FLAG_NEW_LISTENER`
-    * `SECCOMP_FILTER_FLAG_TSYNC_ESRCH`
 
-* **`listenerPath`** *(string, OPTIONAL)* - specifies the path of UNIX domain socket over which the runtime will send the [container process state](#containerprocessstate) data structure when the `SECCOMP_FILTER_FLAG_NEW_LISTENER` flag is specified.
+* **`listenerPath`** *(string, OPTIONAL)* - specifies the path of UNIX domain socket over which the runtime will send the [container process state](#containerprocessstate) data structure when the `SCMP_ACT_NOTIFY` action is used.
     This socket MUST use `AF_UNIX` domain and `SOCK_STREAM` type.
     The runtime MUST send exactly one [container process state](#containerprocessstate) per connection.
     The connection MUST NOT be reused and it MUST be closed after sending a seccomp state.
     If sending to this socket fails, the runtime MUST [generate an error](runtime.md#errors).
-    This field MUST be set if and only if the flag `SECCOMP_FILTER_FLAG_NEW_LISTENER` is used.
+    If the `SCMP_ACT_NOTIFY` action is not used this value is ignored.
 
     The runtime sends the following file descriptors using `SCM_RIGHTS` and set their corresponding indexes in the `fdIndexes` map of the [container process state](#containerprocessstate):