Nick Milas wrote:
On 14/2/2012 11:21 μμ, Nick Milas wrote:
Following the fix of ITS 7098, now (after upgrading to a version with
the fix) I changed successfully the values of OIDs
1.3.6.1.4.1.25260.1.00x to 1.3.6.1.4.1.25260.1.x. (No service stop
followed.)
Yet, after these changes, we could
On 17/2/2012 10:07 πμ, Howard Chu wrote:
Yes, the OID is included in the index computation.
Thank you.
Could/Should the software automatically reindex the directory after OID
change or - if not possible - inform the administrator with a message
that such reindexing should be done manually?
Nick Milas wrote:
On 17/2/2012 10:07 πμ, Howard Chu wrote:
Yes, the OID is included in the index computation.
Thank you.
Could/Should the software automatically reindex the directory after OID
change or - if not possible - inform the administrator with a message
that such reindexing should
On 29/11/2011 12:44 πμ, Quanah Gibson-Mount wrote:
I would suggest you file an ITS with this backtrace and the steps on
how to reproduce it (the ldapmodify of the OIDs).
I have filed ITS #7098
(http://www.openldap.org/its/index.cgi/Incoming?id=7098).
Nick
Hello,
In my config there is:
DN: cn={5}postfix,cn=schema,cn=config
objectClass: olcSchemaConfig
cn: {5}postfix
olcAttributeTypes: {0}( 1.3.6.1.4.1.25260.1.000 NAME
'mailacceptinggeneralid' DESC 'Defines an address that we accept mail
for' EQUALITY caseIgnoreMatch SUBSTR
--On Monday, November 28, 2011 7:09 PM +0200 Nick Milas
n...@eurobjects.com wrote:
When I try to change attribute OID value, for example:
1.3.6.1.4.1.25260.1.000 to 1.3.6.1.4.1.25260.1.0 (using a visual LDAP
client) then the server hangs and will not restart. (I had to restore
from backup and
On 28/11/2011 9:04 μμ, Quanah Gibson-Mount wrote:
If you are using the latest OpenLDAP, I would suggest you get a
backtrace of the hung process and file an ITS. I would note that
changing an OID on an existing schema is a bit of an odd thing to do.
I am using 2.4.26. I'll try to do a core
--On Monday, November 28, 2011 9:18 PM +0200 Nick Milas
n...@eurobjects.com wrote:
On 28/11/2011 9:04 μμ, Quanah Gibson-Mount wrote:
If you are using the latest OpenLDAP, I would suggest you get a
backtrace of the hung process and file an ITS. I would note that
changing an OID on an existing
On 28/11/2011 9:24 μμ, Quanah Gibson-Mount wrote:
2.4.26 is probably fine. You shouldn't need to take a core dump, just
a full backtrace of the hung process.
I.e., gdb /path/to/slapd pid
OK, I hope I've done it right (I'm inexperienced with gdb).
Please check whether sufficient
--On Tuesday, November 29, 2011 12:33 AM +0200 Nick Milas
n...@eurobjects.com wrote:
Here is the gdb output. First is a backtrace before the error occurs:
Just to note, a backtrace from before an error occurs is almost never
useful. ;)
On 29/11/2011 12:33 πμ, Nick Milas wrote:
Please check whether sufficient information has been logged, so I can
file a meaningful ITS.
Also, until a bug fix is made and a release which includes the fix is
published, is there a way we can change the OID values?
It would not be easy for me
--On Tuesday, November 29, 2011 12:48 AM +0200 Nick Milas
n...@eurobjects.com wrote:
On 29/11/2011 12:33 πμ, Nick Milas wrote:
Please check whether sufficient information has been logged, so I can
file a meaningful ITS.
Also, until a bug fix is made and a release which includes the fix is
12 matches
Mail list logo
