[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: about usage of `sigaction'
From: |
William Xu |
Subject: |
Re: about usage of `sigaction' |
Date: |
Fri, 19 Jan 2007 11:49:39 +0800 |
User-agent: |
Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.92 (gnu/linux) |
Kevin Ryde <address@hidden> writes:
> William Xu <address@hidden> writes:
>>
>> So all other things are blocked during accept()?
>
> Signals for the thread in question at least :(.
>
>> Maybe this is a problem of scheme accept?
>
> It's not a good thing, though fixing it might be tricky.
>
> Do you actually need to know immediately the child exits?
Currently it just makes me feel uncomfortable when it doesn't work as
expected.. I hope someday it could get fixed.
> Perhaps it's enough to reap on the next connection. If you need to
> know then you might keep a pipe open to each child, then `select' on
> them plus the listening port. Whichever has some action (incoming
> connect or exited child) can show up.
Yes, that could be a workaround. Thanks.
--
William
If the American dream is for Americans only, it will remain our dream
and never be our destiny.
-- Ren'e de Visme Williamson