On Sat, Sep 3, 2011 at 4:38 AM, Les Mikesell
<lesmikesell AT gmail DOT com> wrote:
In general, backuppc needs rw permission on everything, and apache
(www-data on debian/ubuntu) needs read access to some of it.
Sorry to need such hand-holding, but if I'm above my TOPDIR and execute
chown -R backuppc TOPDIR
chgrp -R www-data TOPDIR
chmod 644 TOPDIR
should that be OK?
Anyone with suggestions for improvement would be most welcome
And what if my CONF and LOG folders are included there as well?
The above is what I was doing when resetting log and pc during my testing.
>> Should I recreate the empty folders and then reset permissions, or just let BackupPC do it - which I assume it would do correctly?
>> Does the message "link host-name" in my log when running "_dump -v" manually indicate a hardlinkng problem kicking in **after** the pc filesystem's already been created?
>>In the past I was running the init start/stop via sudo - would that have messed things up?
Should I run the start/stop with su backuppc instead?
------------------------
I've now tried to uninstall/re-install twice times without success. Apparently the failure of the hardlink test during the postinstall also prevented the creation of the default
config.pl and hosts files.
This time I'm planning to delete the backuppc user as well as:
/var/lib/backuppc
/etc/backuppc
/var/log/backuppc
/usr/share/backuppc
I'm not going to do anything different with the filesystem until I get the default install working first, but I'd really rather not have to re-install the server platform OS itself. . .
is there **anything** else I should do to ensure a "clean" system state before re-installing BackupPC?
