On Wed, 26 Jan 2000, Yevmenkin, Maksim N, CSCIO wrote:
> > > I've just found that read from /dev/bpfX never return
> > EAGAIN/EWOULDBLOCK.
> > > It means that when you do a non blocking read and there is
> > no data you will
> > > always get 0.
> [ untested fix removed :) ]
>
> Yes, it works.
Bruce,
[...]
> > I've just found that read from /dev/bpfX never return
> EAGAIN/EWOULDBLOCK.
> > It means that when you do a non blocking read and there is
> no data you will
> > always get 0.
> >
> > Does it suppose work this way?
>
> I think it is a bug. Perhaps applications depend on it.
On Mon, 24 Jan 2000, Yevmenkin, Maksim N, CSCIO wrote:
> All,
>
> I've just found that read from /dev/bpfX never return EAGAIN/EWOULDBLOCK.
> It means that when you do a non blocking read and there is no data you will
> always get 0.
>
> Does it suppose work this way?
I think it is a bug. Per
