Control socket activation
Compare changes
Files
10+ 38
− 9
@@ -321,7 +321,7 @@ static struct worker_ctx *init_worker(struct engine *engine, knot_mm_t *pool, in
@@ -335,12 +335,18 @@ static int run_worker(uv_loop_t *loop, struct engine *engine, fd_array_t *ipc_se
@@ -364,6 +370,14 @@ static int run_worker(uv_loop_t *loop, struct engine *engine, fd_array_t *ipc_se
@@ -374,6 +388,7 @@ int main(int argc, char **argv)
@@ -457,11 +472,25 @@ int main(int argc, char **argv)
@@ -563,7 +592,7 @@ int main(int argc, char **argv)
While one control socket per process group is something that I'd like to do in the future - what's the benefit from taking it from systemd?
The benefit is that the socket can be placed somewhere that the non-privileged user has no write permissions. I want to start kresd in a fully-unprivileged mode.