https://bugs.openldap.org/show_bug.cgi?id=9697
Issue ID: 9697
Summary: healthcare software development
Product: website
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: website
Assignee: bugs(a)openldap.org
Reporter: ritesh.patil732(a)gmail.com
Target Milestone: ---
https://mobisoftinfotech.com/industry/healthcare-software-development
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6949
--- Comment #11 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
For reference, with the test008 config, timings for progs/slapd-tester -H
ldap://:9011 -D cn=manager,dc=example,dc=com -w secret -d testdata -P progs -l
1000
-s0 -dnone 18.92 seconds
-s0 -d256 23.37 seconds
-s0 -d256 + rotate 27.00 seconds
-s256 -dnone 45.33 seconds
Logfile params were
logfile testrun/logfile
logfile-rotate 12 10 1
logfile-only true
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9464
Issue ID: 9464
Summary: Test suite file conf.sh tries to sed unused items
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
The conf.sh script tries to sed values that are not meant for replacement but
instead are environment variables handled by run.in and defines.sh. This
should be deleted from conf.sh
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9694
Issue ID: 9694
Summary: Can Delta-sync’s changelog be based on a sessionlog?
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
In the replication terminology, the terms sessionlog and accesslog are used.
sessionlog is created by the syncprov-overlay/syncprov-sessionlog directive;
accesslog is created in first place by the accesslog overlay.
Delta-syncrepl introduces an additional term: changelog. The example at
https://www.openldap.org/devel/admin/replication.html#Delta-syncrepl%20Prov…
uses accesslog for the changelog.
The documentation is unclear, whether the changelog must be backed on
accesslog-database, or it can be backed also on a sessionlog. (⇔Is delta-sync
happy just with a sessionlog?)
The documentation in slapo-syncprov(5) for syncprov-nopresent says “This value
should only be set TRUE for a syncprov instance on top of a log database (such
as one managed by the accesslog overlay).”
Is sessionlog a log database?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7595
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=9687
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8341
--- Comment #9 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Re25:
• 2a537ad0
by Ondřej Kuzník at 2021-09-14T16:17:45+00:00
ITS#8341 Allow normalised values for namingContexts in cn=monitor
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8341
--- Comment #8 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
RE26:
• ea92405a
by Ondřej Kuzník at 2021-09-14T16:17:25+00:00
ITS#8341 Allow normalised values for namingContexts in cn=monitor
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8341
--- Comment #7 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
• bfe3d19e
by Ondřej Kuzník at 2021-09-09T10:26:06+01:00
ITS#8341 Allow normalised values for namingContexts in cn=monitor
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9619
Issue ID: 9619
Summary: mdb_env_copy2 with MDB_CP_COMPACT in mdb.master3
produces corrupt mdb file
Product: LMDB
Version: 0.9.29
Hardware: All
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: kriszyp(a)gmail.com
Target Milestone: ---
When copying an LMDB database with mdb_env_copy2 with the MDB_CP_COMPACT with
mdb.master3, the resulting mdb file seems to be corrupt and when using it in
LMDB, I get segmentation faults. Copying without the compacting flag seems to
work fine. I apologize, I know this is not a very good issue report, as I
haven't had a chance to actually narrow this down to a more
reproducible/isolated case, or look for how to patch. I thought I would report
in case there are any ideas on what could cause this. The segmentation faults
always seem to be memory write faults (as opposed to try fault on trying to
read). Or perhaps the current backup/copying functionality is eventually going
to be replaced by incremental backup/copying anyway
(https://twitter.com/hyc_symas/status/1315651814096875520). I'll try to update
this if I get a chance to investigate more, but otherwise feel free to
ignore/consider low-priority since the work around is easy.
--
You are receiving this mail because:
You are on the CC list for the issue.