Package: bacula-director-mysql Version: 5.0.2-1 Severity: normal
this was originally reported in Ubuntu here: https://launchpad.net/bugs/689327 When the dbname parameter is left blank, the bacula-dir.conf that is generated generates this syntax error when bacula-dir is started: dbconfig-common: writing config to /etc/dbconfig-common/bacula-director-mysql.conf Creating config file /etc/dbconfig-common/bacula-director-mysql.conf with new version Processing configuration...Ok. * Starting Bacula Director... 13-12月 02:13 bacula-dir: ERROR TERMINATION at lex.c:784 Config error: expected a string, got T_EOL: = : line 236, col 12 of file /etc/bacula/bacula-dir.conf dbname = ; DB Address = ""; dbuser = ""; dbpassword = "" ...fail! I believe this could be corrected by simply wrapping the value in quotes in the postinst script. This also affects the postgres backend. -- System Information: Debian Release: squeeze/sid APT prefers maverick-updates APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 'maverick') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-23-generic (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
