kqueue oddity

2006-04-01 Thread Václav Haisman
Hi, I have a little problem with kqueue/kevent. I am getting somewhat strange events from kevent(). The struct kevent's contents looks like this: kevent {.ident = 1, .filter = 0xfffe, .flags = 0x0001, .fflags = 0x, .data = 0x84c6} .ident == 1 is stdout. .filter == 0x fffe is

Re: kqueue oddity

2006-04-01 Thread Dan Nelson
In the last episode (Apr 01), Vclav Haisman said: Hi, I have a little problem with kqueue/kevent. I am getting somewhat strange events from kevent(). The struct kevent's contents looks like this: kevent {.ident = 1, .filter = 0xfffe, .flags = 0x0001, .fflags = 0x, .data =

Re: kqueue oddity

2006-04-01 Thread Václav Haisman
Dan Nelson wrote: In the last episode (Apr 01), Vclav Haisman said: Hi, I have a little problem with kqueue/kevent. I am getting somewhat strange events from kevent(). The struct kevent's contents looks like this: kevent {.ident = 1, .filter = 0xfffe, .flags = 0x0001, .fflags =

Re: kqueue oddity

2006-04-01 Thread John-Mark Gurney
Vclav Haisman wrote this message on Sat, Apr 01, 2006 at 20:35 +0200: Dan Nelson wrote: In the last episode (Apr 01), Vclav Haisman said: Hi, I have a little problem with kqueue/kevent. I am getting somewhat strange events from kevent(). The struct kevent's contents looks like this:

Re: kqueue oddity

2006-04-01 Thread Dan Nelson
In the last episode (Apr 01), Vclav Haisman said: Dan Nelson wrote: It's a kqueue bug, but a minor one. The problem is that the same flags field is used to pass actions from the client, and return status from the kernel. When you call kqueue with EV_ADD, the kernel never clears the