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.
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.
Peter
--
Peter Dufault ([EMAIL PROTECTED]) Realtime development, Machine control,
HD Associates, Inc. Fail-Safe systems, Agency approval
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
