Hi all:
Figured I should start a new thread on this as it is a separate
problem from the SIGPIPE issue.
I have a backup hanging until the SIGALARM triggers some 20 hours
later.
The (partial) config is:
$Conf{XferMethod} = 'rsync';
$Conf{RsyncClientPath} = '/usr/bin/rsync';
Trying to split theads here. In a prior discussion on the hang issue,
on Fri, Oct 26, 2007 at 11:13:14AM -0500, Les Mikesell wrote:
John Rouillard wrote:
[rouilj]
$Conf{ClientTimeout} = 72000;
which is 20 hours and the sigpipe is occurring
before then. You'd see sigalarm instead of
John Rouillard wrote:
open(/usr/local/src/fastforward-0.51/warn-auto.sh,
O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
read(3, #!/bin/sh\n# WARNING: This file w..., 64) = 64
close(3)= 0
select(2, NULL, [1], NULL, {60,
On Fri, Oct 26, 2007 at 03:28:28PM -0500, Les Mikesell wrote:
John Rouillard wrote:
open(/usr/local/src/fastforward-0.51/warn-auto.sh,
O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=64, ...}) = 0
read(3, #!/bin/sh\n# WARNING: This file w..., 64) = 64
close(3)
John Rouillard wrote:
Do you mean this select?
select(2, NULL, [1], NULL, {60, 0}) = 1 (out [1], left (line 2799)
{60, 0})
My C is rusty, but I think that means:
look at no fd's for reading and fd 1 for writing and no fd's for
errors. Time out in 60.000 seconds.
What I
Sent this via personal email. Here is the copy for the
list.
On Fri, Oct 26, 2007 at 06:01:16PM -0500, Les Mikesell wrote:
John Rouillard wrote:
again indicates that fd 1 is available for writing. an 8 byte write is
done then fd 0 is checked to see if there is anything to read
write(1,
