Project

General

Profile

Actions

Bug #4229

closed

conf parsing gives very confusing message if no '=' present on setting line

Added by Dan Mick about 11 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

A doc bug caused a user to attempt to include settings of the form

public network <addr>

i.e. missing the equals sign. The config parsing ended up saying

"unexpected character while parsing putative key value, at char N line M", where N was "one past EOL".
The problematic code calls #, ;, and '\0' all "illegal characters in key names", which they are,
but, '\0' should probably be handled differently, issuing something like "no value found on line M; missing =?"

Actions

Also available in: Atom PDF