> No, the main problem I've had is with winexe timeout on one specific
> destination machine, however, I'm pretty sure that is a networking issue
> (ie, there seems to be a flaky DSL connection in the way). I've tried to
> add a few things to detect the timeout and kill winexe (because it
> doesn't seem to timeout by itself), but this doesn't always work.
> Sometimes, backuppc ends up launching multiple copies (one attempt per
> backup window), which I login and kill manually.
>
> Regards,
> Adam

To alleviate that sort of problem, I use this snippet (from my preusercmd
script):

--

$WINEXE --interactive=0 -U $UNAME -W $WRKGRP --password=$PWD //$BOX 'cmd
/c c:\backuppc\pre-exec.cmd' <&- &
pid=$!
# Wait 5 minutes
echo "sleep 300; kill $pid > /dev/null 2>&1" | at now
wait $pid &> /dev/null
if [ $? -ne 143 ]; then
   exit 100
fi

--

Note that I close stdin -- beats me why, but if I don't do this, winexe
has a tendency to run away occasionally.

------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612 
_______________________________________________
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/