On Wed, Apr 17, 2013 at 6:08 PM, Michael Ströder mich...@stroeder.com wrote:
Howard Chu wrote:
Michael Ströder wrote:
From a practical standpoint - behavior of the service when clients are
making
requests to a backend that gets removed is totally undefined.
LDAP clients do not care about
--On Thursday, April 18, 2013 7:18 AM -0300 Diego Woitasen
di...@woitasen.com.ar wrote:
I know that I could remove it from the filesystem, but I wouldn't.
You can use slapcat -n 0 to export your cn=config database to LDIF. Modify
the LDIF for cn=config to no longer reference back-shell,
Quanah Gibson-Mount wrote:
--On Thursday, April 18, 2013 7:18 AM -0300 Diego Woitasen
di...@woitasen.com.ar wrote:
I know that I could remove it from the filesystem, but I wouldn't.
You can use slapcat -n 0 to export your cn=config database to LDIF. Modify
the LDIF for cn=config to no
--On Thursday, April 18, 2013 4:58 PM +0200 Michael Ströder
mich...@stroeder.com wrote:
Quanah Gibson-Mount wrote:
--On Thursday, April 18, 2013 7:18 AM -0300 Diego Woitasen
di...@woitasen.com.ar wrote:
I know that I could remove it from the filesystem, but I wouldn't.
You can use slapcat
Hi,
I was using shell backend and now switched to sock backend (shell
looks unstable). My problem not is that I can't delete the shell DB.
This is the entry in cn=config:
dn: olcDatabase={3}shell,cn=config
objectClass: olcShellConfig
objectClass: olcDatabaseConfig
olcDatabase: {3}shell
When I
Diego Woitasen wrote:
I was using shell backend and now switched to sock backend (shell
looks unstable). My problem not is that I can't delete the shell DB.
This is the entry in cn=config:
dn: olcDatabase={3}shell,cn=config
objectClass: olcShellConfig
objectClass: olcDatabaseConfig
On Wed, Apr 17, 2013 at 12:52 PM, Michael Ströder mich...@stroeder.com wrote:
Diego Woitasen wrote:
I was using shell backend and now switched to sock backend (shell
looks unstable). My problem not is that I can't delete the shell DB.
This is the entry in cn=config:
dn: olcDatabase={3
Michael Ströder wrote:
Diego Woitasen wrote:
I was using shell backend and now switched to sock backend (shell
looks unstable). My problem not is that I can't delete the shell DB.
This is the entry in cn=config:
dn: olcDatabase={3}shell,cn=config
objectClass: olcShellConfig
objectClass
Diego Woitasen wrote:
On Wed, Apr 17, 2013 at 12:52 PM, Michael Ströder mich...@stroeder.com wrote:
Diego Woitasen wrote:
I was using shell backend and now switched to sock backend (shell
looks unstable). My problem not is that I can't delete the shell DB.
This is the entry in cn=config
Howard Chu wrote:
From a philosophical standpoint - production configurations generally only
grow.
IMO this general assumption is not valid.
If you're mucking around and experimenting, you do that on a throw-away
development system.
Well, one should always experiment on a dedicated test
Michael Ströder wrote:
From a practical standpoint - behavior of the service when clients are making
requests to a backend that gets removed is totally undefined.
LDAP clients do not care about (OpenLDAP) database backends at all.
They simply query a DIT.
Yes, but they expect to get
Howard Chu wrote:
Michael Ströder wrote:
From a practical standpoint - behavior of the service when clients are
making
requests to a backend that gets removed is totally undefined.
LDAP clients do not care about (OpenLDAP) database backends at all.
They simply query a DIT.
Yes, but
12 matches
Mail list logo