Re: patch adding a pidfile-option to script(1)

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

I wrote

> There is no promise that stdio is signal-unsafe only when the signal
> interrupts a stdio call, though that is the way most implementations
> happen to work.

Actually, this is true for only a restricted subset of stdio calls.
Some stdio calls can malloc(), and malloc-family calls are not
signal-safe in general (though NetBSD's jemalloc is surprisingly
signal-robust, at least in 9.1).

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse%rodents-montreal.org@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B