Re: copyparty ignores signals (inc. SIGINT)

[Stephen Borrill <netbsd%precedence.co.uk@localhost>]

On Sat, 13 Dec 2025, RVP wrote:
> On Fri, 12 Dec 2025, Stephen Borrill wrote:
>
> > I've been testing copyparty on NetBSD 10.1
> > https://github.com/9001/copyparty
> >
> > It runs just fine, but ignores signals such as SIGINT, so you can't quit 
> > without kill -9.
> >
> > The same versions of copyparty and python work as expected on FreeBSD 14.3
> > and OpenBSD 7.8, so there's something a bit funky about NetBSD's signal 
> > handling here.
>
> Hmm. In FreeBSD, OpenBSD & Linux, pthread_sigmask(3) seems to apply 
> per-thread,
> but on NetBSD, the whole process gets blocked--not just the thread which 
> called
> pthread_sigmask():

In case it's a clue, I found that the signal isn't entirely ignored, but 
it takes 10 minutes to take effect:

builder10# copyparty
[snip]
^Z[1] + Suspended               copyparty
builder10# bg
[1] copyparty &
builder10# date
Thu Dec 18 13:18:10 GMT 2025
builder10# kill -INT %1
builder10# fg
OPYTHAT
15:28:20.051 hsrv                  ok bye
15:28:20.051 tcpsrv                ok bye
15:28:20.051 up2k                  writing snapshot
15:28:20.111 root                  nailed it
builder10#

Note the bad pun so that if you type Ctrl-C it is meant to display 
^COPYTHAT

--
Stephen