I can understand why you want user backuppc when you are potentially
writing files such as when dumping/restoring/deleting backups as
having the wrong perms could cause unexpected results and damage.
However, why is user backuppc required simply to uncompress & cat
files (BackupPC_zcat) or to similarly print an attrib file?
- If the underlying file is readable by the user, why require
additional user perms?
- If the underlying file is not readable then the file system will
deny access automatically and signal the appropriate error.
In particular, I added my user name to the backuppc group, so why
shouldn't I be able to read the files to which I have group read
access?
This can be fixed by simply changing the following line in the
relevant perl scripts from:
die("BackupPC::Lib->new failed\n") if ( !(my $bpc =
BackupPC::Lib->new) );
to:
die("BackupPC::Lib->new failed\n") if ( !(my $bpc =
BackupPC::Lib->new("","","",1)) );
Any reason not to make such a change to the source files?
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
