Documentation

Hi all, List what you love about our docs: List what you hate: List what you'd love to see: List what you can help with: Thanks. -- Kind Regards, Gavin Henry.

Re: Documentation Feedback

> I would offer to contribute to the documentation, but due to its lack of usefulness, do not have an understanding of the basic concepts myself. The best I would be able to do is describe my experience and provide the steps that I followed to get a basic installation working. > > Hopefully

Re: Documentation Feedback

> I would offer to contribute to the documentation, but due to its lack of usefulness, do not have an understanding of the basic concepts myself. The best I would be able to do is describe my experience and provide the steps that I followed to get a basic installation working. > > Hopefully

Re: Export issue after an DN change

--On Friday, April 29, 2016 3:49 PM +0200 mdii wrote: Thanks for the reply. The OpenLDAP version is 2.4.35. For the backend, I'm not really sure where to look at, but I found the attribute olcDbDirectory in the olcDatabase={1}mdb,cn=config entry. It points at the

Antw: Re: Q: "dn: cn=Uptime,cn=Time,cn=Monitor" non-monotonic occasionally?

>>> "Brett @Google" schrieb am 29.04.2016 um 11:50 in Nachricht

Antw: Re: Q: "dn: cn=Uptime, cn=Time, cn=Monitor" non-monotonic occasionally?

>>> Howard Chu schrieb am 28.04.2016 um 19:54 in Nachricht <57224e67.7080...@symas.com>: > > Time values are based on the time(3) subroutine, which can also be affected > by > anyone explicitly resetting the system clock. Of course, such an event would > > also be visible on

Antw: Re: Q: "dn: cn=Uptime,cn=Time,cn=Monitor" non-monotonic occasionally?

>>> Michael Ströder schrieb am 28.04.2016 um 19:26 in Nachricht <572247c0.9030...@stroeder.com>: > Ulrich Windl wrote: >> I'm running a NRPE monitor that monitors openLDAP. To compute delta values, >> the NRPE plugin stores the "dn: cn=Uptime,cn=Time,cn=Monitor" reported by

Antw: Re: Q: "dn: cn=Uptime,cn=Time,cn=Monitor" non-monotonic occasionally?

>>> Michael Ströder schrieb am 29.04.2016 um 09:58 in Nachricht <57231425.2080...@stroeder.com>: > Ulrich Windl wrote: > Michael Ströder schrieb am 28.04.2016 um 19:26 in >> Nachricht <572247c0.9030...@stroeder.com>: >>> Ulrich Windl wrote:

Re: Export issue after an DN change

Thanks for the reply. The OpenLDAP version is *2.4.35*. For the backend, I'm not really sure where to look at, but I found the attribute *olcDbDirectory *in the *olcDatabase={1}mdb,cn=config* entry. It points at the folder */custom/data/openldap-data-oldschema*, where I saw two .mdb files

Re: Q: "dn: cn=Uptime, cn=Time, cn=Monitor" non-monotonic occasionally?

On Thu, Apr 28, 2016 at 6:48 PM, Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: > Hi! > > I'm running a NRPE monitor that monitors openLDAP. To compute delta > values, the NRPE plugin stores the "dn: cn=Uptime,cn=Time,cn=Monitor" > reported by openLDAP to compare it with the current

Re: Q: "dn: cn=Uptime, cn=Time, cn=Monitor" non-monotonic occasionally?

Ulrich Windl wrote: > But for both cases I would be unable to detect a restart of the slapd. Rates > may seem negative then. Yes, your monitoring script has to deal with that anyway. But at least the time difference will not be negative. Ciao, Michael. smime.p7s Description: S/MIME

Re: Antw: Re: Q: "dn: cn=Uptime, cn=Time, cn=Monitor" non-monotonic occasionally?

Ulrich Windl wrote: > Actually you gave a clue: the slapd is running in a VM, and the VM had been > live-migrated. Maybe the glitch originated from there. VMs and time synchronisation are often an issue. I expected it to be something like this. Note that if you setup MMR this can cause some

Re: Q: "dn: cn=Uptime, cn=Time, cn=Monitor" non-monotonic occasionally?

Ulrich Windl wrote: Michael Ströder schrieb am 28.04.2016 um 19:26 in > Nachricht <572247c0.9030...@stroeder.com>: >> Ulrich Windl wrote: >>> I'm running a NRPE monitor that monitors openLDAP. To compute delta > values, >>> the NRPE plugin stores the "dn: