Hello,
I have 5 different locations and want use MMR. I could configure the
replication in a chain,
but if on *in* the chain fails, the complete replication fails. So is
it a good idea to configure/organize
the replication circularly? If one of the "replication member" fails,
the replication betwe
Le mercredi 08 février 2012 à 15:49 -0500, Daniel Savard a écrit :
> Le mercredi 08 février 2012 à 12:09 -0800, Quanah Gibson-Mount a écrit :
>
> >
> > As noted numerous times on this list, "stable" is generally a meaningless
> > term. Use 2.4.28 or if you delay long enough, 2.4.29 when it come
Hello,
In file misc.schema, included in the standard OpenLDAP distribution, we
read about the Lachman/Laser mail routing schema (which defines
inetLocalMailRecipient objectClass with mailLocalAddress, mailHost,
mailRoutingAddress attributes, drafted e.g. here:
http://www.sendmail.org/m4/laser
On 9/2/2012 7:08 μμ, Charles T. Brooks wrote:
I wish I could help more than I have, Nick, but as far as I know there
is no useable RFC standard for mail routing that covers real world
needs. Working pragmatic implementations are based on someone's
interpretation of an expired internet draft, at
On Wed, Feb 08, 2012 at 12:55:34PM +0200, Buchan Milne wrote:
> My implementation is shipped in my openldap packages (with symlinks in cron.*
> enabled for daily backups by default), you can find the scripts here:
> http://svnweb.mageia.org/packages/cauldron/openldap/current/SOURCES/ldap-hot-
> db
On Tue, Feb 07, 2012 at 04:53:52PM -0500, Brian Reichert wrote:
> I'm curious if the tactics described in this thread are currently
> sufficient:
>
> http://www.openldap.org/lists/openldap-software/200608/msg00152.html
Let me try asking a slightly different question.
This page says:
http://
--On Thursday, February 09, 2012 2:21 PM -0500 Brian Reichert
wrote:
Follow-up: is it expected that the misc db_* utilities can be used
safely at this point?
The only officially supported backup method with OpenLDAP is slapcat.
Everything else, you do at your own risk. Personally, I think
On 7/2/2012 11:53 μμ, Brian Reichert wrote:
I'm curious if the tactics described in this thread are currently
sufficient:
http://www.openldap.org/lists/openldap-software/200608/msg00152.html
We are using CentOS 5.7 too. Upgrade from 2.3.43 as has been suggested
already; it caused us seve
On Thu, 09 Feb 2012 12:54:27 -0800, Quanah Gibson-Mount
wrote:
The only officially supported backup method with OpenLDAP is slapcat.
Everything else, you do at your own risk.
The admin guide disagrees with you. Chapter 19 describes incremental
backup by copying first the entire DB, then bac
--On Thursday, February 09, 2012 11:12 PM +0100 Hallvard B Furuseth
wrote:
On Thu, 09 Feb 2012 12:54:27 -0800, Quanah Gibson-Mount
wrote:
The only officially supported backup method with OpenLDAP is slapcat.
Everything else, you do at your own risk.
The admin guide disagrees with you.
Hi everyone,
I am trying to implement Kerberos authentication and I believe I am
almost there, however when I run the ldapwhoami command I am getting a
segmentation fault rather than a success message. Here is the output of
the ldapwhoami (yes, I have a Kerberos ticket):
SASL/GSSAPI authenticatio
Hi,
One or two question about certificate compatibility,
I have self signed certificate generated by openSSL, and the official
package of openldap in Ubuntu is compilated with gnutls library. Do you
think this configuration could create error ?
If this is the case, and if i want to maintain t
Hallvard B Furuseth wrote:
On Thu, 09 Feb 2012 12:54:27 -0800, Quanah Gibson-Mount
wrote:
The only officially supported backup method with OpenLDAP is slapcat.
Everything else, you do at your own risk.
The admin guide disagrees with you. Chapter 19 describes incremental
backup by c
On Thu, 09 Feb 2012 14:36:20 -0800, Howard Chu wrote:
Hallvard B Furuseth wrote:
The only officially supported backup method with OpenLDAP is
slapcat.
Everything else, you do at your own risk.
The admin guide disagrees with you. Chapter 19 describes
incremental
backup by copying first
--On Thursday, February 09, 2012 5:15 PM -0500 Daniel Savard
wrote:
Hi everyone,
I am trying to implement Kerberos authentication and I believe I am
almost there, however when I run the ldapwhoami command I am getting a
segmentation fault rather than a success message. Here is the output of
t
Le jeudi 09 février 2012 à 23:21 +0100, rey sebastien a écrit :
> Hi,
>
> One or two question about certificate compatibility,
> I have self signed certificate generated by openSSL, and the official
> package of openldap in Ubuntu is compilated with gnutls library. Do you
> think this configurat
On Thu, Feb 09, 2012 at 02:36:20PM -0800, Howard Chu wrote:
> Hallvard B Furuseth wrote:
> > On Thu, 09 Feb 2012 12:54:27 -0800, Quanah Gibson-Mount
> >wrote:
> >
> >>The only officially supported backup method with OpenLDAP is slapcat.
> >>Everything else, you do at your own risk.
> >
> > Th
I wrote:
On Thu, 09 Feb 2012 14:36:20 -0800, Howard Chu wrote:
Chapter 19 is obviously a work-in-progress, transferred over from
the
FAQ-o-Matic.
Presumably because backup has previously only been described in
the FAQ-o-Matic. But I'm pretty sure this has been the documented
backup method w
--On Thursday, February 09, 2012 4:35 PM -0500 Brian Reichert
wrote:
I do know that using the db_* utilities are only applicable to the
BDB backend. As far as I know, it's the most mature of the backends
to use with 2.3.43. (If I'm wrong in that, do let me know.)
2.3 is not a supported rele
On 02/09/12 17:15 -0500, Daniel Savard wrote:
Hi everyone,
I am trying to implement Kerberos authentication and I believe I am
almost there, however when I run the ldapwhoami command I am getting a
segmentation fault rather than a success message. Here is the output of
the ldapwhoami (yes, I hav
On Thu, Feb 09, 2012 at 03:09:41PM -0800, Quanah Gibson-Mount wrote:
> 2.3 is not a supported release series. I would strongly advise upgrading
> to a supported release.
Having tracked this project for years, I'm well aware of that stance,
but I'm trapped in a world where I'm stuck with what the
--On Thursday, February 09, 2012 5:17 PM -0500 Brian Reichert
wrote:
What we're doing currently is:
- stopping slapd
- using db_checkpoint and db_archive to manage the BDB logs
- copy away the directory
- restart slapd
I'm trying to estabish if read-only mode is close enough to _stopping_
s
On Thu, Feb 09, 2012 at 03:48:45PM -0800, Quanah Gibson-Mount wrote:
> I thought I was very clear on that in my last email. It is not sufficient.
> You need to stop slapd and run *db_recover*, which is more exhaustive than
> db_checkpoint, if you want to go the route of backing up the BDB db.
I
--On Thursday, February 09, 2012 5:30 PM -0500 Brian Reichert
wrote:
I'm sorry; I thought you were focussing on my processing of the
directory's contents (which do need review, thanks), rather than
how I prepared slapd.
Ok. Now I now, read-only mode via the config database is not
sufficient
Hi,
I have ldap clients on two different OS platforms, Solaris and Linux.
When "shadowExpire" for a specific user is set, the Linux client sees
the change and denies logon for the user which is what I'm trying to
implement. But this behaviour doesn't work in my Solaris client. It
seems like it doe
On Thursday, 9 February 2012 21:00:36 Brian Reichert wrote:
> On Wed, Feb 08, 2012 at 12:55:34PM +0200, Buchan Milne wrote:
> > My implementation is shipped in my openldap packages (with symlinks in
> > cron.* enabled for daily backups by default), you can find the scripts
> > here:
> > http://svnw
26 matches
Mail list logo
