Re: Is KQueue still broken on Darwin?

In article <1327i8uinfdkk99@[EMAIL PROTECTED]
>,
 SM Ryan <wyrmwif@[EMAIL PROTECTED]
> wrote:

> Gregory Weston <uce@[EMAIL PROTECTED]
> wrote:
> # In article <13277khfed5tv24@[EMAIL PROTECTED]
>,
> #  SM Ryan <wyrmwif@[EMAIL PROTECTED]
> wrote:
> # 
> # > I have a program that gets in an uninterruptible wait for
> # > hours and days. I'm using sockets and kqueue. I have never
> # > had problems with sockets before, but kqueue used to crash
> # > the kernel. Does anyone know if kqueue still borks the machine?
> # 
> # It never has for me. What's the nature and cir***stance of the 
> # misbehavior you're seeing?
> 
> It hangs on customer machines not mine where I cannot examine it
> too closely (no gdb, etc). It monitors the file system, running
> kqueue on up to 2000 disk inodes. It has a unix domain socket
> to another process. When I look at with ps -x the status is Us.
> If I kill the companion process, one of the threads will abort
> the entire process on a broken pipe; then the status is Es and
> it's still hung.
> 
> This can persist for days, until someone notices it. The only
> recovery I know of is a reboot. I do know kqueue panicked 10.3.
> I wonder if it's still broken or 10.4.9 broke it.

I've got a few thousand users running a program that's been reliant on 
kqueue for ... about 2.5 years now. Seems like there's got to me more 
detail than "kqueue panicked 10.3."

What I'm kind of getting at is that maybe you're not looking at the 
right culprit.