Date: Sun, 3 Dec 2000 13:18:03 -0500 (EST) From: Daniel Eischen <eischen@vigrid.com> To: Peter Dufault <dufault@hda.com> Cc: hackers@FreeBSD.ORG Subject: Re: Arg! Siginfo and pthreads again Message-ID: <Pine.SUN.3.91.1001203131433.10999A-100000@pcnet1.pcnet.com> In-Reply-To: <200012031548.KAA61923@hda.hda.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.1001203131433.10999A-100000>