dnscrypt-proxy doesn't kill its child process if the main process is stopped

[konimex]

Description

When the main dnscrypt-proxy program/service (root) is stopped, the child process is still running. This means if I restart the dnscrypt-proxy service, it would fail since there's already a dnscrypt-proxy instance running.

Expected

The child process is also killed along with its parent process.

Actual result

The child process still runs under init.

I'm not sure if this is intended or a bug. But I'm leaning towards the latter.

[jedisct1]

What operating system is that on? How are you stopping it? Using dnscrypt-proxy -service stop?

[konimex]

Artix Linux, using runit as init system. (Also testing on Void Linux to see if this problem only exists on Artix or also happens on Void)Also happened on Void.

I stopped it using sv stop dnscrypt-proxy command provided by runit.

[jedisct1]

Do you know how to fix this?

[konimex]

I think when the main process caught SIGTERM from the service manager (in this case, runit), kill its child process (if any). However I'm not sure if the main process tracks its child, and I'm not well-versed in Go.