On Sun, 3 Dec 2000, Peter Dufault wrote:
> Again I've forgotten that SIGINFO dumps the pthread info and created
> several gigabytes of /tmp files:
>
> > rt% rm /tmp/uthread*
> > /bin/rm: Argument list too long.
>
> I don't consider it bad form to use SIGINFO to see if processes are
> still around without first installing a SIGINFO handler.
Can't you use `kill -0 pid` if you just want to see if the process
is around?
> Am I the only one ever burnt by this?
> Do other user-space thread systems handle this similarly?
> Maybe an info thread can block at an info fifo in conjunction
> with a "psthread" program.
Now that we can accomodate more than 31 signals, we could always
add a SIGTHRINFO (or something more aptly named) instead of using
SIGINFO.
--
Dan Eischen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
