Modify

Ticket #397 (closed defect: fixed)

Opened 15 years ago

Last modified 15 years ago

Confusing question for bcfg -I

Reported by: naapuri Owned by: desai
Priority: minor Milestone: Bcfg2 0.9.2 Release
Component: bcfg2-client Version:
Keywords: Cc:

Description

bcfg2 -I asks a question, but it doesn't look like a question:

/var/lib/mysql/my.cnf group wrong. is mysql should be root

It should probably read something like:

/var/lib/mysql/my.cnf group is mysql, should be root. Fix? (y/N):

Attachments

Change History

comment:1 Changed 15 years ago by desai

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone set to Bcfg2 0.9.2 Release

comment:2 Changed 15 years ago by naapuri

  • Priority changed from trivial to minor
  • Status changed from closed to reopened
  • Resolution fixed deleted

Reopening.

The questions still don't look like questions. The above now says:

/var/lib/mysql/my.cnf group is mysql should be root

while it should say:

/var/lib/mysql/my.cnf group is mysql, should be root. Fix? (y/N):

The problem gets worse when there are more than one thing wrong with a config file. All anomalies are printed at once (which is good), so there should only be one "Fix?" question:

/var/lib/mysql/my.cnf owner wrong. is mysql should be root
/var/lib/mysql/my.cnf group is mysql should be root
/var/lib/mysql/my.cnf perms are 0775 should be 0755

Alternative fix is to ask three questions, but that will be annoying.

comment:3 Changed 15 years ago by desai

  • Status changed from reopened to closed
  • Resolution set to fixed

This is now fixed properly; a single question is displayed regardless of the set of incorrect details.

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.