Subject: Re: better signal delivery to threads
To: None <M.Drochner@fz-juelich.de>
From: Zeljko Vrba <firstname.lastname@example.org>
Date: 08/22/2005 21:27:06
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Matthias Drochner wrote:
> leftover of another script executed previously, or perhaps
> related to logging) which don't block the signal in question,
IIRC POSIX, this is OK - any thread not blocking the signal can receive it.
> (This might be technically not the fault of NetBSD's libpthread.
hm.. did you try to report this to the Python mailing list? I think it's
more appropriate place. why patch kernel if the SW running on it is broken?
[and I'm pretty, although not 100%, sure that NetBSD is _not_ at fault
> Using threads and signals to processes together is just a bad idea.
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----