In the last episode (Oct 04), Trond Endrestol said:
> On Tue, 4 Oct 2011 18:51+0200, Dag-Erling Smorgrav wrote:
> > Trond Endrestol writes:
> > > It's in daily use at Gjovik Technical College (Fagskolen i Gjovik),
> > > here in Norway. Both the mail and web servers authenticates our users
> > > b
On Tue, 4 Oct 2011 17:20+0200, Dag-Erling Smørgrav wrote:
> Does anyone actually use nscd?
It's in daily use at Gjøvik Technical College (Fagskolen i Gjøvik),
here in Norway. Both the mail and web servers authenticates our users
by LDAP, and nscd certainly speeds up the lookups.
Trond.
--
-
On Wed, 5 Oct 2011 12:54+1030, Daniel O'Connor wrote:
> On 05/10/2011, at 2:30, Michel Talon wrote:
>
> > Des wrote:
> >> Does anyone actually use nscd?
> >
> > I am using it since a lot of time. I have not experienced annoying bugs
> > in all that time. The last time i have been hit is when ins
On Tue, 4 Oct 2011 18:51+0200, Dag-Erling Smørgrav wrote:
> Trond Endrestøl writes:
> > It's in daily use at Gjøvik Technical College (Fagskolen i Gjøvik),
> > here in Norway. Both the mail and web servers authenticates our users
> > by LDAP, and nscd certainly speeds up the lookups.
>
> OK.
2011/10/5 Dag-Erling Smørgrav :
> Michael Bushkov writes:
>> 2. Consequences of the aforementioned problem can probably be
>> corrected by using _setsockopt(..., SO_NOSIGPIPE) in
>> __open_cached_connection() in nscachedcli.c
>
> That sounds like a workaround rather than a fix...
Not necessarily.
Michael Bushkov writes:
> 2. Consequences of the aforementioned problem can probably be
> corrected by using _setsockopt(..., SO_NOSIGPIPE) in
> __open_cached_connection() in nscachedcli.c
That sounds like a workaround rather than a fix...
DES
--
Dag-Erling Smørgrav - d...@des.no
__
There are probably 2 things here:
1. There's some error in nsswitch<->nscd communication protocol that
causes nsswitch to write into the closed socket. This is not trivial
to investigate and will require analyzing nscd and client process logs
side by side (and possibly adding some more logging).
2.
2011/10/5 Michael Bushkov :
> There are probably 2 things here:
> 1. There's some error in nsswitch<->nscd communication protocol that
> causes nsswitch to write into the closed socket. This is not trivial
> to investigate and will require analyzing nscd and client process logs
> side by side (and
2011/10/4 Dag-Erling Smørgrav :
> Any chance of getting a backtrace from an unpatched nscd? Ideally with
> the change described here:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/136073#reply1
>
> To test, stop nscd, then run it from the command line like so:
>
> $ su -
> # cd /tmp
> # ulimi
On 5 October 2011 23:12, Nathan Whitehorn wrote:
> Can you explain why the critical section is there in more detail? It seems
> like all of our problems arise because of it.
It seems to make some of my MIPS cases more problematic. I don't know
about the i386. DES reports that his weird/crashing
Hello,
I'm looking into the code of 4.4BSD scheduler (and related files) of FreeBSD
version 7.2-RELEASE on an amd64 machine in order to understand how to manage
time slices. I'm trying to dynamically change the length of the time slice on a
thread by thread basis to "give more priority" or "less
On Wednesday 05 October 2011 10:46:47 Eugene Grosbein wrote:
> 04.10.2011 22:47, Sean M. Collins пишет:
> > I've never heard of the utility until you mentioned it.
> >
> > I'd nuke it, since really there are more popular alternatives like Redis
> > and Memcached in the ports tree that most people
On 10/01/11 04:25, Alexander Motin wrote:
Hi.
Adrian Chadd wrote:
What happens if this occurs:
* cpu_idle() is entered
* you enter critical_enter() and call cpu_idleclock()
* an interrupt occurs, scheduling an immediate callout
* .. but you've already set the clock register, so it won't be
ser
04.10.2011 22:47, Sean M. Collins пишет:
> I've never heard of the utility until you mentioned it.
>
> I'd nuke it, since really there are more popular alternatives like Redis
> and Memcached in the ports tree that most people will reach for first.
>
Please look at http://www.freebsd.org/cgi/que
On 05/10/2011 09:43, Dag-Erling Smørgrav wrote:
> While we're at it, I'd be very grateful if someone could email me a
> quick and dirty guide to setting up an LDAP server for testing. I have
> too much on my plate right now to start reading documentation...
The Quick Start guide on the OpenLDAP s
On 05/10/2011, at 19:13, Dag-Erling Smørgrav wrote:
> "Daniel O'Connor" writes:
>> I'd be interested in testing your workaround(s) :)
>
> It wasn't a workaround, actually, just a one-line change that enables
> additional logging (when running with from the console -nst) which might
> help me fig
"Daniel O'Connor" writes:
> I'd be interested in testing your workaround(s) :)
It wasn't a workaround, actually, just a one-line change that enables
additional logging (when running with from the console -nst) which might
help me figure out why it crashes. See my reply to Artem Belevich
earlier
Lawrence Stewart writes:
> If the machine running nscd loses connectivity with the DNS server for
> a while and does a DNS lookup during that time, nscd will cache the
> -ve reply indefinitely for all users, which breaks all sorts of
> crap. Have to forcibly run "nscd -I all" to fix. I will find a
18 matches
Mail list logo
