enterprise-support team mailing list archive

[Max Bubenick <max.bubenick@xxxxxxxxxxx>]

Public bug reported:

{ "no-locks", 'k', 0, G_OPTION_ARG_NONE, &no_locks, "Do not execute the temporary shared read lock.  WARNING: This will cause inconsistent backups", NULL },
105107        { "long-query-guard", 'l', 0, G_OPTION_ARG_INT, &longquery, "Set long query timer in seconds, default 60", NULL },
106108        { "kill-long-queries", 'k', 0, G_OPTION_ARG_NONE, &killqueries, "Kill long running queries (instead of aborting)", NULL },

both are using k, this was introduce with no-locks. We need to change it
to K

** Affects: mydumper
     Importance: Medium
     Assignee: Max Bubenick (max-bubenick)
         Status: Triaged

** Changed in: mydumper
    Milestone: None => 0.6.2

** Changed in: mydumper
     Assignee: (unassigned) => Max Bubenick (max-bubenick)

** Changed in: mydumper
   Importance: Undecided => Medium

** Changed in: mydumper
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1336860

Title:
  k is used twice

To manage notifications about this bug go to:
https://bugs.launchpad.net/mydumper/+bug/1336860/+subscriptions