Mageia RPM specific notes Setup ----- The Mageia setup improves the FHS compliance wrt. that used upstream: - /var/www/backuppc ... files accessible from the web - /usr/share/backuppc ... files non-accessible from the web - /var/lib/backuppc ... files with varibales - /etc/backuppc ... both global and per-host configuration files Backuppc user; backup-data -------------------------- Backup-data stored in another file-system can be made accessible to backuppc by creating a soft link from /var/www/lib to the root of the backup-data hierarchy. If backuppc is uninstalled (urpme backuppc), this data will not be deleted - with the exception of a cpool directory that is empty; when, subsequently, backuppc is newly installed, cpool must be manually created (with uid:gid = backuppc:backkuppc). To make backuppc access backup-data that exist prior to installing backkuppc, make sure that the user "backuppc" exists BEFORE the package is installed, and that its uid and gid matches the ownership of that data (otherwise the package would automatically create the user with random uid and gid values). Lighttpd server definition -------------------------- When using lighttpd, the following definition in /etc/lighttpd/lighttpd.conf should work: ["url"] =~ "^/backuppc" { server.document-root = "/var/www/backuppc" cgi.assign = ( "BackupPC_Admin" => "" ) index-file.names = ( "BackupPC_Admin" ) alias.url = ( "/backuppc" => "/var/www/backuppc" ) dir-listing.activate = "disable" ["remoteip"] != "127.0.0.1" { auth.backend = "htpasswd" auth.backend.htpasswd.userfile = "<password-dir>/passwd/backuppc" auth.require += ( "" => ( "method" => "basic", "realm" => "BackupPC", "require" => "valid-user" ) ) } } <password-dir> is the directory where you keep the passwords for your server; the suggested definition does not require authentication if the backuppc gui is invoked from the machine that hosts the lighttpd server