Nils Breunese (Lemonbit) wrote:
>>> Apologies for the relatively long email, but I figure it's better to
>>> give too much information than not enough. I've run into a bit of
>>> difficulty backing up a large directory tree that has me not being
>>> able to do a successful backup in over a month now. I'm attempting to
>>> back up about 70GB over the Internet with a 1 MB/sec connection (the
>>> time it takes doesn't really bother me, just want to do a full backup
>>> and then run incrementals all the time). However, the transfer always
>>> times out with signal=ALRM.
>>
>> ALRM should mean the server's $Conf{ClientTimeout} expired. You may
>> need to make it much longer. The time is supposed to mean inactivity but
>> some circumstances make it the total time for a transfer to complete.
>>
>> signal=PIPE means the connection broke or the client side quit
>> unexpectedly.
>
> Although the ALRM and PIPE signals are probably technically correct it
> might be clearer to use different terms/explanations in the interface. I
> have the feeling not everyone understands these signals.
man signal
will show all the possibilities. SIGPIPE isn't very clear because it
really just means a child process terminated while the parent is still
trying to communicate with it, but in this case the child is the ssh,
rsync, or smbclient that is doing the transfer from the remote and the
likely reasons are either a network problem or that the remote side
terminated.
--
Les Mikesell
[EMAIL PROTECTED]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
