On Thu, Jul 09, 2009 at 10:34:08AM +0200, Wouter Verhelst wrote: > On Wed, Jul 08, 2009 at 11:00:42PM +0200, Jaap Eldering wrote: > > Package: nbd-server > > Version: 1:2.9.11-3 > > Severity: grave > > Justification: renders package unusable > > No it doesn't. > > > Running nbd-server results in an error that a configuration file cannot > > be parsed or found: > > > > $ nbd-server 1234 /some/file > > > > ** (process:9399): WARNING **: Could not parse config file: Could not open > > config file. > > It's a *warning*, not an error. nbd-server will happily continue with > the command-line specified configuration if it can't parse the config > file, but will give you a warning message that the config file could not > be read. > > Since you specified a port and a filename, nbd-server should be running > and waiting for a client to connect at this point. > > > $ nbd-server 1234 /some/file -C /usr/share/nbd-server/nbd-server.conf.tmpl > > > > ** (process:9401): WARNING **: Could not parse config file: Unknown error > > That is an incomplete template file to be used by the debconf > configuration scripts. By itself, it indeed is an invalid configuration > file.
Ok, sorry for my overly quick bug report, I hadn't checked whether nbd-server was actually running and assumed it didn't because of the error/warning message. Still, I think that there's something to be improved here: nbd-server gives this warning without any other message that it has started. This message looks pretty serious, especially since the man-page explicitly states that a non-existent or empty config file can be specified without problem. I'd suggest to make it clear in the warning message that nbd-server is still started and/or update the documentation about this message. Or maybe add a default configuration file which nbd-server can parse and which removes this warning message? Jaap -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
