Package: bacula-director-sqlite Version: 1.36.1-1 Followup-For: Bug #285755
I think we can chalk this up to a corrupt database. Kind of bad that sqlite was crashing due to this, but it doesn't seem to be a problem with bacula-director after all. Please close this at your leisure, and thanks for the help! Jeff -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.9a Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages bacula-director-sqlite depends on: ii bacula-common 1.36.1-1 Network backup, recovery and verif ii bacula-director-common 1.36.1-1 Network backup, recovery and verif ii debconf 1.4.30.11 Debian configuration management sy ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an ii libgcc1 1:3.4.3-6 GCC support library ii libsqlite0 2.8.15-3 SQLite shared library ii libstdc++5 1:3.3.4-13 The GNU Standard C++ Library v3 ii libwrap0 7.6.dbs-6 Wietse Venema's TCP wrappers libra ii sqlite 2.8.15-3 A command line interface for SQLit -- debconf information: * bacula-director-sqlite/remove_catalog_on_purge: false * bacula-director-sqlite/create_tables: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
