Re: (ITS#6331) slapd freezing, not accepting further 'write' operations while 'read' operations are unaffected

[j@telepaths.org]

OK, I'm not going to waste any more of your guys' time, nor mine.

I am going to abandon the use of OpenLDAP forever.  I've spent the  
last three years learning it as well as possible and its not getting  
me anywhere.

I own 7 books on the subject - and they're mostly crap. What one  
doesn't cover, the other covers in 'vague' detail.  The man pages for  
OpenLDAP suck, mostly.  And when you complain on this point, someone's  
response is to "write one better".  Well professor, If I knew enough  
to WRITE my own manpage, why the hell would i be READING one???

I almost sold my soul to Satan to attend LDAPcon2009 - didn't work  
out, so I couldn't.  My only desire to go to this event was to meet  
Howard Chu, anyway.

I'm tired of all of this crap.

In one release, MultiMaster isn't supported.

In the next, it IS supported, but has SyncRepl issues in 2.4.11  -  
kind of a BIG PROBLEM, don't you think??

In 2.4.17, it has dead-lock issues, causing a server to lock up and no  
longer accept WRITES, but will continue to allow READS - I can't even  
fathom how or why this is considered 'acceptable'.

and now, in 2.4.19, I'm getting:

Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0x43662950 (LWP 11001)]
0x00007fb10ea8275b in write () from /lib/libpthread.so.0

... during my GDB debugging session. FOR NO REASON.

This is in ADDITION to the SegFaults i received yesterday (the reason  
for which I was USING gdb in the 1st place).

I'm completely done using your Software.  OpenLDAP's quality has  
irretrievably gone down hill, and I'm sorry, but I'm tired of spending  
most of my career trying to build the PERFECT directory server only to  
find out that its not stable (but sadly, does EVERYTHING we want).   
OpenLDAP is no longer an industry capable suite, it is not reliable,  
replication is a joke (doesn't log ADD operations???), stable  
MultiMaster is a LIE,  everything is poorly documented and it is  
genuinely disappointing on so many levels that I won't waste your time  
by stating them here.  From my reading, the only way I will ever be  
satisfied with "LDAP" is by going with a Sun implementation, since it  
offers EVERYTHING we currently have & want from LDAP, except its  
probably got good documentation and support that I can rely on for  
enterprise-level needs.

I've read some posts on your site, suggesting the need to 'revamp'  
some of slapd's code.  My suggestion to you guys is GET ON IT NOW.

I want to thank Pierangelo and Quanah for being the more 'active'  
participants in my cries for help.

Please close the following tickets, since I'm never going to try any  
of this ever again:

ITS # 6320
ITS # 6331

Forgive my loss of patience, but you'd be upset too if something  
you've devoted the last three years of your career was beginning to  
resemble "a lost cause" that requires unending attention.  My job  
requires results, not full-time LDAP analyst.

Thanks again, farewell.

Jeff