* Matthew Dillon <[EMAIL PROTECTED]> [030109 12:37] wrote: > Well, the manual page (which may be out of date) infers > that the rfork() only operates on the current process if > RFPROC is not set. If we extend that to include RFTHREAD > then the inference is that either RFPROC or RFTHREAD must be > set and if neither is set an error should be returned. Am > I missing something?
That sounds right. The only reason I didn't go that far was because I wasn't sure if we wanted to allow shared sigacts without leadership. I think that it would be safest to require userland to set either RFPROC or RFTHREAD. Yes, the manpage is out of date. What the hell is a sigact anyhow? Can someone please fixup the manpage? :) -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
