On 9/20/19 11:31 AM, Bernd Fix wrote: > It was correctly noted that using Ctrl-C to interrupt the running > service (if started as a foreground process) does not work in all cases. > This is due to the intrinsics of the Go runtime (see > https://github.com/golang/go/issues/21905 for this) and unlikely to be > fixable in user code. > > This might be annoying as normal GNUnet services can be terminated that > way, but I consider it acceptable for a program designed to run as a > background process. Sending signals (SIGTERM, SIGINT) to the process > works fine, using SIGKILL is discouraged as may leave remnants (socket > files) behind that need to be removed manually.
Mea culpa - what a stupid mistake... The Ctrl-C issue is not related to what I thought it was (Go runtime problem, had that issue in other projects before), but to malformed switch clauses in signal handling. I have corrected the error in the gnunet-go repository. Cheers, Bernd. _______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
