[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: spurious connection_read()s

To: Quanah Gibson-Mount <quanah@stanford.edu>
Subject: Re: spurious connection_read()s
From: Aaron Richton <richton@nbcs.rutgers.edu>
Date: Fri, 16 Jun 2006 11:26:47 -0400 (EDT)
Cc: openldap-software@OpenLDAP.org
In-reply-to: <AFF53E7373B39D5FED12AA55@SW-90-717-287-3.stanford.edu>
References: <Pine.SOL.4.58.0606160844060.7470@toolbox.rutgers.edu> <AFF53E7373B39D5FED12AA55@SW-90-717-287-3.stanford.edu>

> This is solaris, right?  I think it is a side effect of the solaris file
> descriptor kernel bug.

Wasn't there a workaround in place for that?

Not that I think a workaround is such a terrific idea. If I should be
yelling at Sun, I'll yell at Sun. But is there something in the world a
bit less complex than slapd that can prove wrong Solaris behavior? It
would be good to hand them a test case that's smaller than 150KLOC. Or if
its a known issue that needs votes, a Solaris bug id would be more useful
than a test case.

Follow-Ups:
- Re: spurious connection_read()s
  - From: Quanah Gibson-Mount <quanah@stanford.edu>

References:
- spurious connection_read()s
  - From: Aaron Richton <richton@nbcs.rutgers.edu>
- Re: spurious connection_read()s
  - From: Quanah Gibson-Mount <quanah@stanford.edu>

Prev by Date: Re: spurious connection_read()s
Next by Date: Re: spurious connection_read()s
Index(es):
- Chronological
- Thread