search for: do_extended

...ot match for user 'lblin'! ############################################# LDAP LOGS: ------------------------- ldap_pvt_gethostbyname_a: host=obiwan, r=0 connection_get(9): got connid=0 connection_read(9): checking for input on id=0 ber_get_next ber_get_next: tag 0x30 len 29 contents: do_extended ber_scanf fmt ({a) ber: ber_get_next ber_get_next on fd 9 failed errno=11 (Resource temporarily unavailable) send_ldap_extended 0: (0) send_ldap_response: msgid=1 tag=120 err=0 ber_flush: 14 bytes to sd 9 connection_get(9): got connid=0 connection_read(9): checking for input on id=0 TLS trace: SSL_...

...eserve case = yes case sensitive = no ---------------------------------------------------------------------------- --------------- The error that occurred while samba talking to ldap on my PDC and only there not on my BDC: EXT oid=1.3.6.1.4.1.1466.20037 Apr 8 09:22:20 tuepdc slapd[7693]: do_extended: unsupported operation "1.3.6.1.4.1.1466.20037" Apr 8 09:22:20 tuepdc slapd[7693]: conn=441 op=0 RESULT tag=120 err=2 text=unsupported extended operation No user could logon to the PDC nor did the account of the workstations longer work. The chaos was, that the Samba BDC only served a...

...use the domain DOMAINNAME is unavailable." While this is certainly not the case, at least in this situation the user is informed that the password change did not work. I can see that LDAP does indeed pass back a response to Samba; from the LDAP logs: Apr 4 10:47:37 servername slapd[12709]: do_extended Apr 4 10:47:37 servername slapd[12709]: >>> dnPrettyNormal: <uid=tester,ou=Users,dc=example,dc=com> Apr 4 10:47:37 servername slapd[12709]: <<< dnPrettyNormal: <uid=tester,ou=Users,dc=example,dc=com>, <uid=tester,ou=users,dc=example,dc=com> Apr 4 10:47:37 serv...

...passdb backend = ldapsam:"ldap://127.0.0.1/" ldap ssl = Off so samba schouldn't use ssl, or? why is there this error message? in my slapd log i have this messages http://pastebin.jan500.org/234 the most import i think is: Sep 8 22:17:21 boss slapd[7532]: conn=0 op=0 do_extended: unsupported operation "1.3.6.1.4.1.1466.20037" Sep 8 22:17:21 boss slapd[7532]: send_ldap_result: conn=0 op=0 p=3...

All, Please review the patches backported to 1.4 from mainline. Sunil

Hi, the first four patches in this series fix locking problems in OCFS2 quota code (three of them can lead to potential deadlocks). The fifth patch reorders ip_alloc_sem for directories to be acquired before localalloc locks. Mark would you please merge these? The last two patches implement lockdep annotations for OCFS2 cluster locks. We annotate all the cluster locks except for special ones

Hi, I'm resending this patch series. It's rediffed against linux-next branch of Joel's git tree. The first four patches are obvious fixes of deadlocks in quota code and should go in as soon as possible. The other three patches implement lockdep support for OCFS2 cluster locks. So you can have a look whether the code make sence to you and possibly merge them. They should be NOP when

The following patches implement indexed directory support in Ocfs2, mostly according to the design doc I wrote up a while ago: http://oss.oracle.com/osswiki/OCFS2/DesignDocs/IndexedDirectories The patches have been rebased on top of 2.6.29-rc2. It should be trivial to put them into merge_window. Things are what I'd call complete now. I'd like to get these into the merge_window branch

The following series of patches attempts to detach metadata I/O from struct inode. They are currently tied together pretty tightly. Metadata reads happen via the ocfs2_read_blocks() functions, writes via both jbd2 and ocfs2_write_blocks(). - Each inode has a cache of associated metadata blocks stored on its ip_metadata_cache member. The ocfs2_read/write_blocks() functions take a struct

Hi, The following patches comprise the bulk of Ocfs2 updates for the 2.6.30 merge window. Aside from larger, more involved fixes, we're adding the following features, which I will describe in the order their patches are mailed. Sunil's exported some more state to our debugfs files, and consolidated some other aspects of our debugfs infrastructure. This will further aid us in debugging