bugGNU dbm - Bugs: bug #566, The max-failed-keys option of the...

Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

bug #566: The max-failed-keys option of the recover is unavailable.

Submitted by:  zhangxiaofeng <zhagnxiaofeng>
Submitted on:  Fri Jun 17 12:28:57 2022  
Category: NonePriority: 5 - Normal
Severity: 5 - NormalStatus: Fixed
Privacy: PublicAssigned to: Sergey Poznyakoff <gray>
Open/Closed: Closed

Sat Jun 18 14:27:44 2022, comment #1:

Thanks for reporting. Fixed in b8271d89db991558e10c26d45d960bbc0257fa31

Sergey Poznyakoff <gray>
Project AdministratorIn charge of this item.
Fri Jun 17 12:28:57 2022, original submission:

[root@localhost ~]# gdbmtool junk.gdbm list
1 one
2 two
[root@localhost ~]# echo 0 >> junk.gdbm
[root@localhost ~]# gdbmtool junk.gdbm

Welcome to the gdbm tool. Type ? for help.

gdbmtool> list
stdin:1.1-5: gdbm_firstkey: Database needs recovery
gdbmtool> recover max-failed-keys=1
stdin:2.1-24: syntax error, unexpected '=', expecting '\n' or ';'

zhangxiaofeng <zhagnxiaofeng>


No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by gray (Posted a comment)
  • -unavailable- added by zhagnxiaofeng (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    3 latest changes follow.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat Jun 18 14:27:44 2022grayStatusNone=>Fixed
      Assigned toNone=>gray
    Show feedback again

    Back to the top

    Powered by Savane 3.1-cleanup+gray