Hi Stefan

On 12/03/2012 01:42 AM, Stefan Peter wrote:
> Hi Gary
>
> On 01.12.2012 02:35, Gary Roach wrote:
>
>    
>> Everything worked fine for /etc. /root and /var. When I tried to backup
>> / home the system chugged along for a long time and then went to sleep.
>>      
> You mean the system went into sleep mode during the restore?
>    
Yes. That appears to be the case. A system info tool I have showed the 
process to be "waiting for reply". What ever that means.
>    
>> I had to manually stop the process by killing the PID.
>> The restore log had the following entries:
>>
>>      2012-11-30 09:53:41 Started restore on TargetComputer (pid=7601)
>>      2012-11-30 10:59:23 Restore failed on TargetComputer (aborted by
>>      signal=TERM)
>>      
> What else did you expect after having it killed?
>    
Exactly that. Just included the whole file.
>    
>>      2012-11-30 10:59:23 TargetComputer: File::RsyncP::FileList::encode:
>>      missing rdev
>>      
> This and the following "missing rdev" messages seem to indicate that the
> backup does not contain a value for the device ID for these files. In
> all the errors you have showed, only pipes seem to be affected. This may
> either indicate that backuppc does not properly handle pipes or that the
> rsync configuration during the backup of these files was missing the -D
> switch.
>
> However, this is not a problem: I'd assume that KDE will silently
> recreate the pipes if they are missing. If not, you still can recreate
> them from the command line using the mkfifo command.
>    
I think the missing D switch is definitely the problem.
>> I use
>> inetd.conf to start the rsync daemon with an entry of :
>>
>>      rsync   stream  tcp  nowait   root  /usr/bin/rsync   rsyncd --daemon
>>
>> If the -D switch must be included, should it be something like rsyncd -D
>> daemon.
>>      
> The rsync daemon in general uses /etc/rsyncd.conf for configuration. The
> only options it accepts are listed in the man pages under the heading
> "DAEMON OPTIONS" and those only deal with network parameter and daemon
> behavior. The -D option needs to be present n the client side (and it
> needed to be there during backup, too).
>
>    
You seem to imply that the D switch should be included as an entry in 
the rsyncd.conf file. Unfortunately, there is no place for switches in 
that file. The closest thing is the "socket options"  parameter in the 
"global parameters" module. After some research of "setsockopt" I found 
no indication that the D option applies to that parameter.

Would The D switch inclusion in the rsync string in the inetd.conf file 
work (ie the end of the string being 'rsyncd -D --daemon' or some such.)

> Regards
>
> Stefan Peter
>
>    
I really appreciate the help

Gary R.

------------------------------------------------------------------------------
Keep yourself connected to Go Parallel: 
BUILD Helping you discover the best ways to construct your parallel projects.
http://goparallel.sourceforge.net
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/