Python signal delivery under BSD 4.4

[Donn Cave]

Quoth "Elf M. Sternberg" <elf at drizzle.com>:
| ...  But, fortunately, we're
| developing a single-OS appliance and don't really care about
| cross-platform compatibility, so I worked with the FreeBSD 4.4 "model"
| of forking from multithreaded applications.  It's fortunate that the
| next call is an exec(); I'd hate to have to manage a forked copy of the
| process with that one thread...

So, you resolved the problem and the spawnv child process can now
receive signals?  Did you use sigprocmask() to clear the signal
mask?  What is the FreeBSD 4.4 model of forking from multithreaded
applications?  (And is it the same as the FreeBSD 4.7 model, 5.1, etc.?)

	Donn Cave, donn at drizzle.com