Yeah, I don't see it either why it is affected :) I can try hGetContents from home.
Thanks, Michael On Fri, 10 Dec 2004 19:12:39 +0000, Keean Schupke <[EMAIL PROTECTED]> wrote: > Hmm, I dont see why the main process would be affected... It should be able > to accept multiple connections in parallel. > > Is it just hGetLine that causes the problem... what if you use hGetContents > instead? Does it still not work? > > (I have a sever implemented - I tested it with "ab -n100 -c10" with no > problems...) > > Keean. > > > > Michael Walter wrote: > > >I did that -- the main process doesn't die, anyway, it just seems to "hang". > > > >- Michael > > > > > >On Fri, 10 Dec 2004 16:27:05 GMT, MR K P SCHUPKE > ><[EMAIL PROTECTED]> wrote: > > > > > >>>But if the forkIO'ed process terminates because of an exception, that > >>>shouldn't influence the main process, right? > >>> > >>> > >>Well, if its unix you might have to set sigPIPE to Ignore... > >> > >>Otherwise, the main process should not die just because the child has... > >> > >> Keean. > >> > >> > >> > > _______________________________________________ Haskell-Cafe mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell-cafe