So I encountered this issue a long while back but recently ran into it again. When tinc is compiled as a static binary it takes sending a kill command twice to truly kill the process. On the first kill command I do see the following entries in the log
killall tincd
Aug 2 17:51:26 R7000 daemon.notice tinc[10380]: Got Terminated signal
Aug 2 17:51:26 R7000 daemon.notice tinc[10380]: Terminating
However, the process hasn't completely exited and is still found running using top or ps.
On the second invocation of "killall tincd" then the process is actually killed.
I was reminded of this when running the meson tests because everything was failing and I had a dozen hanging tincd processes.
So I encountered this issue a long while back but recently ran into it again. When tinc is compiled as a static binary it takes sending a kill command twice to truly kill the process. On the first kill command I do see the following entries in the log
killall tincd
However, the process hasn't completely exited and is still found running using
toporps. On the second invocation of "killall tincd" then the process is actually killed. I was reminded of this when running the meson tests because everything was failing and I had a dozen hanging tincd processes.