Opened 12 years ago
Closed 11 days ago
#51 closed defect (fixed)
db4: rpm databases are still open after closing them
| Reported by: | Yuri Dario | Owned by: | |
|---|---|---|---|
| Priority: | Feedback pending | Milestone: | db ports |
| Component: | bdb | Version: | |
| Severity: | low | Keywords: | |
| Cc: |
Description
While working at rpm rebuilddb issue, I discovered that database files are still locked after closing them; probably somewhere some locking call is not removed when file is closed (or some memory mapping is still there...)
Since we have a few issues with DB4, it is worth investigating this issue and see if it is related to transactional defects shown in rpm.
Change History (3)
comment:1 by , 11 years ago
| Milestone: | → db ports |
|---|---|
| Severity: | → low |
comment:2 by , 9 years ago
| Priority: | major → Feedack pending |
|---|
comment:3 by , 11 days ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I think this is fixed with latest rpm and yum. If not open a ticket at our github
Note:
See TracTickets
for help on using tickets.
is this still true with the latest db4?