Holger Parplies wrote at about 01:56:31 +0100 on Saturday, December 20, 2008:
> Hi,
>
> Adam Goryachev wrote on 2008-12-20 00:55:45 +1100 [Re: [BackupPC-users]
> Permission denied during backup]:
> > In my setup, there are no other files on a "normal" system t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johan Ehnberg wrote:
> > So, probably better to pass --one-file-system to rsync rather than
> > worrying about trying to exclude /proc, /sys, etc...
>
> But then we have to worry about mounts on each client separately to get
> it all backed up, ri
>>> 'ls -la' gives (note the size!)
>>> dr-x-- 2 johan johan 0 2008-12-19 14:39 .gvfs
>> Strange. Even an empty directory needs to contain '.' and '..' entries (and
>> the link count 2 suggests that it does). How any file system would store that
>> in 0 bytes ... maybe in the inode? Mis-i
Glassfox wrote:
>
> anandx wrote:
> > Just do a "whereis sudo" to get the actual path and use the same.
> >
> >
> > > I just don't know what about the arguments
> > > before sudo...
> > >
> >
> > --
> > Thanks and Regards,
> >
> > Anand
> >
>
>
> Ok thanks. Now the backup process does no
anandx wrote:
> Just do a "whereis sudo" to get the actual path and use the same.
>
>
> > I just don't know what about the arguments
> > before sudo...
> >
>
> --
> Thanks and Regards,
>
> Anand
>
Ok thanks. Now the backup process does not want to start. After cancelling I've
seen in the
Just do a "whereis sudo" to get the actual path and use the same.
>I just don't know what about the arguments
>before sudo...
--
Thanks and Regards,
Anand
--
___
BackupPC-us
Nils Breunese (Lemonbit) wrote:
> Glassfox wrote:
>
>
> > It's getting better, but there is still a bug. I think this is this
> > line in the config.pl:
> >
> > $Conf{RsyncClientCmd} = 'sudo $rsyncPath $argList+';
> >
> > Is "sudo" added in right way?
> >
>
> No, you need to supply the fu
Glassfox wrote:
> It's getting better, but there is still a bug. I think this is this
> line in the config.pl:
>
> $Conf{RsyncClientCmd} = 'sudo $rsyncPath $argList+';
>
> Is "sudo" added in right way?
No, you need to supply the full path to sudo, as these commands are
not interpreted by a sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Holger Parplies wrote:
> Hi,
>
> Adam Goryachev wrote on 2008-12-20 00:55:45 +1100 [Re: [BackupPC-users]
> Permission denied during backup]:
>> [...]
>> BTW, not likely relevant in this specific case, but root can't ac
Hi,
Adam Goryachev wrote on 2008-12-20 00:55:45 +1100 [Re: [BackupPC-users]
Permission denied during backup]:
> [...]
> BTW, not likely relevant in this specific case, but root can't access
> all files... damn, in trying to prove this to myself, I noticed it
> didn't wo
Johan Ehnberg wrote:
> Glassfox wrote:
> Did you try the docs I referred? Or is the case that you don't have root
> access at all, in other words you are not able to edit /etc/sudoers?
>
> File permissions work that way - you either need to be root or need to
> set access to the files (see 'ma
Usually backuppc is not run by root but by it's onw user. as you are backing up
the localmachine you don't need ssh to do the file transfer.
Just copy rsync to /opt/BackupPC/bin
chown root:backuppc /opt/BackupPC/bin/rsync
chmod 550 /opt/BackupPC/bin/rsync
chmod u+s /opt/BackupPC/bin/rsync
this
Adam Goryachev wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Johan Ehnberg wrote:
>
>> File permissions work that way - you either need to be root or need to
>> set access to the files (see 'man chown' and 'man chmod'). For secret
>> files, such as cryptographic keys, it is not
Usually backuppc is not run by root but by it's onw user. as you are backing up
the localmachine you don't need ssh to do the file transfer.
Just copy rsync to /opt/BackupPC/bin
chown root:backuppc /opt/BackupPC/bin/rsync
chmod 550 /opt/BackupPC/bin/rsync
chmod u+s /opt/BackupPC/bin/rsync
this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johan Ehnberg wrote:
> File permissions work that way - you either need to be root or need to
> set access to the files (see 'man chown' and 'man chmod'). For secret
> files, such as cryptographic keys, it is not at all feasible to use
> loose perm
Glassfox wrote:
>
> Carl Wilhelm Soderstrom wrote:
>> On 12/18 03:56 , Glassfox wrote:
>>
>>> Hello, I want to backup my localhost completely and just backup the root
>>> folder with some excludes (proc, sys, media and backuppc pool folder).
>>> Backup was successful, but if I look at the error l
Carl Wilhelm Soderstrom wrote:
> On 12/18 03:56 , Glassfox wrote:
>
> > Hello, I want to backup my localhost completely and just backup the root
> > folder with some excludes (proc, sys, media and backuppc pool folder).
> > Backup was successful, but if I look at the error log file there are a l
On 12/18 03:56 , Glassfox wrote:
> Hello, I want to backup my localhost completely and just backup the root
> folder with some excludes (proc, sys, media and backuppc pool folder).
> Backup was successful, but if I look at the error log file there are a lot
> of "Permission denied" errors for the h
Glassfox wrote:
> Hello, I want to backup my localhost completely and just backup the root
> folder with some excludes (proc, sys, media and backuppc pool folder). Backup
> was successful, but if I look at the error log file there are a lot of
> "Permission denied" errors for the home folders, s
Hello, I want to backup my localhost completely and just backup the root folder
with some excludes (proc, sys, media and backuppc pool folder). Backup was
successful, but if I look at the error log file there are a lot of "Permission
denied" errors for the home folders, some files in the /root/
20 matches
Mail list logo
