Full_Name: Pierangelo Masarati Version: irrelevant OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (82.63.140.131) Submitted by: ando
Syncrepl by default uses no retry. This is extremely useless, as syncrepl with no retry will probably break, sooner or later, without notifying why it happened.
I believe it would be safe to have either:
- a "safe" retry value (not too often, e.g. every hour, forever)
- a warning (or an error) if retry is not given when configuring syncrepl
Another interesting feature would be to register syncrepl-specific parameters in back-monitor's entry of each database, that
- show the status of syncrepl (whether it's up, if rp)
- show the timestamp of the last successful refresh
- show the timestamp of the last failed attempt, and the reason of the failure
p.