configure.pl: comments that delimit Conf settings must now start in

    column 1.  This fixes bug when merging new Conf settings that
    have comments embedded in the value.
BackupPC_Admin: improved error message when config.pl cannot be read.
BackupPC.pod: added some items to the roadmap.

diff --git a/cgi-bin/BackupPC_Admin b/cgi-bin/BackupPC_Admin
index 57511ef..99cc594 100755 (executable)
--- a/cgi-bin/BackupPC_Admin
+++ b/cgi-bin/BackupPC_Admin
@@ -1605,8 +1605,12 @@ sub ErrorExit
                             if ( defined($bpc) );
     if ( !defined($Lang->{Error}) ) {
        Header("BackupPC: Error");
+        $mesg = <<EOF if ( !defined($mesg) );
+There is some problem with the BackupPC installation.
+Please check the permissions on BackupPC_Admin.
+EOF
        print <<EOF;
-${h1("Error: Language strings not defined!!")}
+${h1("Error: Unable to read config.pl or language strings!!")}
 <p>$mesg</p>
 EOF
        Trailer();

diff --git a/doc-src/BackupPC.pod b/doc-src/BackupPC.pod
index f5eda7b..59af087 100644 (file)
--- a/doc-src/BackupPC.pod
+++ b/doc-src/BackupPC.pod
@@ -239,7 +239,8 @@ Adding hardlink support to rsync.
 =item *
 
 Adding block and file checksum caching to rsync.  This will significantly
-increase performance.
+increase performance since the server doesn't have to read each file
+twice to compute the block and file checksums.
 
 =item *
 
@@ -250,6 +251,31 @@ you could request that you get sent email if any files below /bin,
 
 =item *
 
+Allow editing of config parameters via the CGI interface. Users should
+have permission to edit a subset of the parameters for their clients.
+Additionally, allow an optional self-service capability so that users
+can sign up and setup their own clients with no need for IT support.
+
+=item *
+
+Add backend SQL support for various BackupPC metadata, including
+configuration parameters, client lists, and backup and restore
+information.  At installation time the backend data engine will
+be specified (eg: MySQL, ascii text etc).
+
+=item *
+
+Disconnect the notion of a physical host and a backup client.
+Currently there is a one-to-one match between physical hosts
+and backup clients.  Instead, the current notion of a host
+should be replaced by a backup client.  Each backup client
+corresponds to a physical host.  A physical host could have
+several backup clients.  This is useful for backing up
+different types of data, or backing up different portions
+of a machine with different frequencies or settings.
+
+=item *
+
 Resuming incomplete full backups.  Useful if a machine
 (eg: laptop) is disconnected from the network during a backup,
 or if the user manually stops a backup.  This would be supported