On Feb 1, 2:09am, Joshua N Pritikin wrote:
> On Tue, Jan 29, 2002 at 06:03:21AM +0100, Marc A. Lehmann wrote:
> > On Mon, Jan 28, 2002 at 06:43:59PM -0500, Allen Smith
> > <[EMAIL PROTECTED]> wrote:
> > > > If an filehandle returns POLLHUP or POLLERR Event goes into an
> > > > endless CPU-eatin
On Tue, Jan 29, 2002 at 06:03:21AM +0100, Marc A. Lehmann wrote:
> On Mon, Jan 28, 2002 at 06:43:59PM -0500, Allen Smith <[EMAIL PROTECTED]>
>wrote:
> > > If an filehandle returns POLLHUP or POLLERR Event goes into an
> > > endless CPU-eating poll-loop.
> >
> > Ouch! Yes, the current code woul
On Mon, Jan 28, 2002 at 06:43:59PM -0500, Allen Smith <[EMAIL PROTECTED]>
wrote:
> > If an filehandle returns POLLHUP or POLLERR Event goes into an
> > endless CPU-eating poll-loop.
>
> Ouch! Yes, the current code would do this... this needs to be fixed,
> definitely.
It's not as if this hasn't
On Jul 24, 7:57pm, wrote:
> I just found that Event goes into an endless polling loop whenever an error
> occurs on a filehandle:
>
>poll([{fd=3, events=POLLPRI|POLLOUT|POLLWRNORM|POLLRDBAND|POLLWRBAND,
>revents=POLLERR|POLLHUP}], 1, 6) = 1
>gettimeofday({995996622, 745496}, NULL)
I just found that Event goes into an endless polling loop whenever an error
occurs on a filehandle:
poll([{fd=3, events=POLLPRI|POLLOUT|POLLWRNORM|POLLRDBAND|POLLWRBAND,
revents=POLLERR|POLLHUP}], 1, 6) = 1
gettimeofday({995996622, 745496}, NULL) = 0
poll([{fd=3, events=POLLPRI|POLL
