On Tue, Jun 23, 2009 at 13:40, Nick Smith wrote:
> Does anyone know if i can change the password to the backuppc user in linux
> and not have any adverse effects with the backuppc system?
>
> On Tue, Jun 23, 2009 at 3:17 PM, Nick Smith wrote:
> > On Tue, Jun 23, 2009 at 2:46 PM, Matthias Meyer
>
Nick Smith wrote:
> Does anyone know if i can change the password to the backuppc user in linux
> and not have any adverse effects with the backuppc system?
>
Yes, you can. The account doesn't actually NEED a password.
Chris
--
Does anyone know if i can change the password to the backuppc user in linux
and not have any adverse effects with the backuppc system?
On Tue, Jun 23, 2009 at 3:17 PM, Nick Smith wrote:
> On Tue, Jun 23, 2009 at 2:46 PM, Matthias Meyer wrote:
>> Nick Smith wrote:
>>>
>>> Ok, new problem, i cant ge
On Tue, Jun 23, 2009 at 2:46 PM, Matthias Meyer wrote:
> Nick Smith wrote:
>>
>> Ok, new problem, i cant get the backuppc user to work with shared keys.
>> Ive added the /var/lib/backuppc/.ssh/id_rsa.pub contents to the other
>> linux box's
> in /root/.ssh I assume.
yes into authorized_keys and _k
[cut]
> That's it, in the log file i see during restore :
Hi Alex,
> connect from UKNOWN x.X.X.X (ip adress)
> receiving file list
> Using VSS Volume : \\?\GLOBALROOT\Device\shadowcopy1
> Error -2147212521 on line 85! (problem writing on vss i think)
> Error -2147024809 on line 100! (again)
>
Nick Smith wrote:
>
> Ok, new problem, i cant get the backuppc user to work with shared keys.
> Ive added the /var/lib/backuppc/.ssh/id_rsa.pub contents to the other
> linux box's
in /root/.ssh I assume.
> authorized_keys and _keys2 file and it always prompts for a password.
> The password
> does
Nick Smith wrote:
>> The root setup on the backuppc server side is irrelevant. You may have
>> set it up in addition to the correct backuppc setup. You don't need it.
>>
>>> The command that backuppc is running in the config is:
>>> $sshPath -q -x -p 22200 -l root $host $rsyncPath $argList+
>>> S
> The root setup on the backuppc server side is irrelevant. You may have
> set it up in addition to the correct backuppc setup. You don't need it.
>
>> The command that backuppc is running in the config is:
>> $sshPath -q -x -p 22200 -l root $host $rsyncPath $argList+
>> So i thought i had to hav
Nick Smith wrote:
>>> Communication working both directions.
>>> r...@backup-server:/root/.ssh# ssh -p 22200 -l root webserver whoami
>>> root
>> You are supposed to be the backuppc user on the backuppc server when you
>> do this test. You are executing it as root.
>>
>
> Whats strange is thats h
>> Communication working both directions.
>> r...@backup-server:/root/.ssh# ssh -p 22200 -l root webserver whoami
>> root
>
> You are supposed to be the backuppc user on the backuppc server when you
> do this test. You are executing it as root.
>
Whats strange is thats how i setup the first linux
Alex wrote:
>
> Jeffrey J. Kosowsky wrote:
> > Alex wrote at about 10:04:12 -0400 on Tuesday, June 23, 2009:
> >
> > >
> > > Hello,
> > > back again, just still experimenting this solution, everything is ok
> > > while reading.
> > >
> > > But, i'm used to restore data on Windows PC using th
Jeffrey J. Kosowsky wrote:
> Alex wrote at about 10:04:12 -0400 on Tuesday, June 23, 2009:
>
> >
> > Hello,
> > back again, just still experimenting this solution, everything is ok while
> > reading.
> >
> > But, i'm used to restore data on Windows PC using the chmod command
> > "--chmod=Dug
Alex wrote at about 10:04:12 -0400 on Tuesday, June 23, 2009:
>
> Hello,
> back again, just still experimenting this solution, everything is ok while
> reading.
>
> But, i'm used to restore data on Windows PC using the chmod command
> "--chmod=Dugo+rwx,Fugo+rwx" to allow user to read fil
Hello,
back again, just still experimenting this solution, everything is ok while
reading.
But, i'm used to restore data on Windows PC using the chmod command
"--chmod=Dugo+rwx,Fugo+rwx" to allow user to read files.
Because rsync runs as daemon under system account, writen files are not
reada
14 matches
Mail list logo