My longest backup is currently 4 hours (75Gb) so I set the timeout to 6
hours.  This solution seems to work fine since one of those timeout
situations occurred yesterday.  It would be nice to find how to stop
smbclient from hitting 100% when backup client gets disconnected but low
timeout value it acceptable workaround for my setup.

Thanks



> -----Original Message-----
> From: Jeffrey J. Kosowsky [mailto:backuppc AT kosowsky DOT org] 
> Sent: Sunday, September 20, 2009 8:49 PM
> To: General list for user discussion, questions and support
> Subject: Re: [BackupPC-users] killing backuppc job after 
> client disconnects
> 
> Marcelino Mata wrote at about 13:47:03 -0400 on Friday, 
> September 18, 2009:
>  > I have been testing backuppc for a few weeks with a dozen 
> Windows  > laptops.  I have chosen smb over rsync protocol 
> for it's setup  > simplicity and it's working well for what I 
> need.  The slower speed of  > smb backup is actually better 
> since the users are not impacted by  > network performance 
> issues with a faster backup protocol like rsync.
>  > I'm running the 3.1 release from the Ubuntu 9.0.4 repo.  
>  >
>  > One outstanding problem is that when a Laptop user 
> disconnects from the  > network, backuppc never terminates 
> the backup job.  It happily continues  > on with "backup in 
> progress" until I manually kill the job from the CGI  > 
> interface.  I just found this posting and I noticed the 
> default time out  > is 20 hours.
>  >
>  > 
> http://sourceforge.net/mailarchive/message.php?msg_id=443678E1
> .8070706%4
>  > 0wpkg.org
>  >
>  > Is the preferred solution to change the ClientTimeout 
> value or is there  > another solution to address this?  Other 
> than monitoring it with a  > background process and sending 
> it a kill command. 
>  >  
> 
> I think a while back we had a discussion about potentially 
> including a test for stalled backups including 'ping' and/or 
> a test on whether data is still being transferred (over a 
> suitably long period of time).
> 
> The trick is coming up with the right 'heuristic' for judging 
> when a backup is truly and irreversibly stalled.
> 
> The problem with ClientTimeout is that it is just an arbitrary number
> - set it too short and you are liable to timeout during 
> backups that are appropriately taking a long time. Set it too 
> long and you have to wait that length until the process is 
> killed and restarted.
> 
> --------------------------------------------------------------
> ----------------
> Come build with us! The BlackBerry® Developer Conference 
> in SF, CA is the only developer event you need to attend this 
> year. Jumpstart your developing skills, take BlackBerry 
> mobile applications to market and stay ahead of the curve. 
> Join us from November 9-12, 2009. Register now! 
> http://p.sf.net/sfu/devconf 
> _______________________________________________
> 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/
> 

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
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/