Re: Synchronous signal delivery..

Keith Adamson
2003-02-14T02:58:54Z

trimmed cc list

> I see that there are several fairly general event sources now:
>
> - signals
> - epoll events
> - async I/O events
> - posix timers
>
> More events that don't provide enough information:
>
> - dnotify details (siginfo doesn't say enough)
> - sigsegv read/write? (siginfo doesn't say enough)
>
> More events that should be accessible but aren't:
>
> - vm paging like crazy, please release some memory
>
> Your synchronous signals code effectively makes signals work with
> select/poll/epoll nicely.

How about also including a connect()/bind() interface so that
you can sort of have a "sockets for signals" type interface.
This seems like a nice type of interface for synchronization.
And maybe use send()/recv() instead of read()/write(). Or am
I on crack:)