linux-traipu team mailing list archive

[Daniel Nichter <daniel@xxxxxxxxxxx>]

I remind us of http://blog.krow.net/2012/02/error-messages.html

Long-term, ultimately, it will really help Drizzle to have some sort of
consistency for its error messages.  I know, for example, that some
people actively watch the error log, particularly when they deploy new
boxes.  The easier, more consistent Drizzle error messages, the easier
it will be to detect when a new box has broken.  And since Drizzle is a
database for the cloud, we should expect Drizzle servers to be
virtualized/puppetized/deployed in automated ways, thereby making checks
for consistency all the more important.

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/943657

Title:
  Better error message on startup / drizzled.cc

Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
  Confirmed

Bug description:
  In drizzled/drizzled.cc several checks are made on startup and if they
  fail then drizzled will abort with an error message.

  For instance if I do

    sbin/drizzled --foo

  then I will get the error

  Aborting:"Use --help to get a list of available options. unknown
  option foo". Abort was called from drizzled/drizzled.cc:1369 in
  init_variables_after_daemonizing()

  This is a result of following code:

    catch (po::unknown_option &err)
    {
      unireg_abort << "Use --help to get a list of available options. " << err.what();

  
  The error message is very confusing, lacks spaces and capitalization. It would be much better if it was worded like this:

  Aborting: Unknown option foo. Use --help to get a list of available options. 
    Abort was called from drizzled/drizzled.cc:1369 in init_variables_after_daemonizing()

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