> I'm using the Concurrent-module to write some daemonish
> programs which use
> Sockets. I use threadWaitRead to suspend the thread to keep it from
> blocking on accept(). The trouble is that the RTS will complain about
> "No threads to run, deadlock?!" after some time.
> Is there any way to prevent this (by command-line option)?
> (Anyways, dying
> because of *that* in a function called *threadWait...* sounds
> a little bit...
> unwise?)
If you're doing this kind of stuff I recommend you use a really up-to-date
GHC (i.e. built from CVS sources), since there have been lots of
changes/fixes in the areas of concurrency & non-blocking I/O in the last few
weeks.
Cheers,
Simon
