RE: [BackupPC-users] Origin and/or implications of "aborted by si gnal=ALRM"?

[Kris B. <Kri...@sc...>]

> -----Original Message-----
> From: Craig Barratt [mailto:cba...@us...]
> Sent: November 1, 2004 12:05 PM
> To: Kris Boutilier
> Cc: Bac...@li...
> Subject: Re: [BackupPC-users] Origin and/or implications of 
> "aborted by signal=ALRM"? 
{clip}
> > Any suggestions on the causes of an Alarm signal, which side it's being
> > generated/received on or what process might be generating it? It looks
like
> > a timeout watchdog kicking in, but the ClientTimeout should be plenty
high
> > enough...
> 
> Yes, it should be.  The only source of an ALRM signal should be
> $Conf{ClientTimeout}.  It is run on the server side.  Are you sure
> there isn't a per-PC config.pl setting for $Conf{ClientTimeout}
> that is a smaller value?
> 

I've just grep'ed through the system and the only occurances I could find
were in config.pl and config.pl~ (a backup file from the 'Joe' editor). I
also checked the configuration reported in the gui and it shows as
'$Conf{ClientTimeout} = 720000' also. 

10 hours sounds pretty close to 32768 seconds... any chance the parameter is
being converted to a short integer somewhere? Regardless, I'm rerunning the
backup with detailed logging this time to see if I've got any more
filesystem wierdness happening. I'll keep you posted.

Thanks.