(ITS#6542) Segmentation Fault if config file (ldif) got changed
by felix.schuster＠gmx.at
Full_Name: Felix
Version: 2.4.19
OS: Linux/Gentoo
URL:
Submission from: (NULL) (78.142.131.97)
Using the new configuration scheme, I changed
/etc/openldap/slapd.d/cn=config/olcDatabase={1}hdb.ldif of a running openldap
instance. When I tried to restart openldap it gaves me a Segmentation Fault
error. Even if I called the changes off, openldap refused to start (furthermore
segfaulted). I needed to get a copy of the original configuration file from my
backup to successfully start openldap again.
I think it's somewhere ok to deny working with a hand-changed configuration, but
I think we will need a friendly advise, no unfriendly Segementation Fault error.
13 years, 4 months
Re: (ITS#6247)
by Kurt＠OpenLDAP.org
On May 1, 2010, at 12:31 PM, daniel(a)pluta.biz wrote:
> Hi,
>=20
> just some changes and cleanups according the still ongoing discussion =
on=20
> ldapext.
I recommend consideration of this patch be deferred until the =
specification is less of a work-in-a-progress.
>=20
> The patch can be downloaded here:=20
> ftp://ftp.openldap.org/incoming/daniel-pluta-100501.patch
>=20
> Changes:
> - removed extensible matching rules strictly associated with=20
> dedicated syntaxes
> - added two universal matching rules instead:
> - nowMach (equality matching rule)
> - nowOrdering (ordering matching rule)
> - these two rules also support extensible match filters
Your comments imply these rules could be used as attribute type equality =
and ordering rules. I don't believe the met the requirements (see =
X.501) to be used in that manner. That is, they only make sense as =
extensible matching rules.
>=20
> To publish a correct server current time time-stamp value within =
Root-DSE:
> - apply the bugfix from ITS#6541
> - and use -DCTM_G_DIFFERENTIAL_SERVERTIME
#ifdef's should, IMO, be generally avoided.
>=20
>=20
> To extend generalizedTime attribute types to also support "NOW" as=20
> assertion value:
> - use -DCTM_RFC4517_MR_AV_SYNTAX_VIOLATION
The generalized time syntax is not ours to alter. Introduction of such =
a change would, it seem, lead to interoperability problems.
>=20
>=20
> Beware of patching conflicts in schema_init.c:
> This patch contains small redundant parts from my parallel =
contribution=20
> in ITS#6532
>=20
> Regards,
> Daniel
>=20
>=20
13 years, 4 months
(ITS#6247)
by daniel＠pluta.biz
Hi,
just some changes and cleanups according the still ongoing discussion on
ldapext.
The patch can be downloaded here:
ftp://ftp.openldap.org/incoming/daniel-pluta-100501.patch
Changes:
- removed extensible matching rules strictly associated with
dedicated syntaxes
- added two universal matching rules instead:
- nowMach (equality matching rule)
- nowOrdering (ordering matching rule)
- these two rules also support extensible match filters
To publish a correct server current time time-stamp value within Root-DSE:
- apply the bugfix from ITS#6541
- and use -DCTM_G_DIFFERENTIAL_SERVERTIME
To extend generalizedTime attribute types to also support "NOW" as
assertion value:
- use -DCTM_RFC4517_MR_AV_SYNTAX_VIOLATION
Beware of patching conflicts in schema_init.c:
This patch contains small redundant parts from my parallel contribution
in ITS#6532
Regards,
Daniel
13 years, 4 months
