In article <13283qfb2h7a4de@[EMAIL PROTECTED]
>,
SM Ryan <wyrmwif@[EMAIL PROTECTED]
> wrote:
> Gregory Weston <uce@[EMAIL PROTECTED]
> wrote:
> # 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."
>
>
http://www.google.com/search?hl=en&safe=off&client=safari&rls=en&q=kqueue+kern
> el+panic&btnG=Search
About 98% of those results don't seem to involve OS X.
A random sample of those that remain suggest that few of them actually
implicate kqueue in kernel panics.
Those that do implicate kqueue in kernel panics describe a fairly
specific scenario that's not particularly common.
That last would be the "more detail" I was interested in. And it doesn't
particularly look like it would be either intermittent or delayed when
it does happen, so it doesn't sound like a good candidate for the source
of your issue.
> It's well known kqueue was broken on 10.3.
To whom? Honestly, I have a hard time accepting that a problem is fairly
described as "well known" if I can sup****t a deployed product that
relies fundamentally on the implicated technology for years without
hearing of it.
G
|
