From: BitTwister@mouse-potato.com   
      
   On Mon, 21 Nov 2022 12:47:13 +0100, Carlos E.R. wrote:   
   > On 2022-11-21 03:04, bad sector wrote:   
   >> On Sun, 20 Nov 2022 15:08:06 -0700, Sidney_Kotic wrote:   
   >>   
   >>> On 11/20/22 07:02, bad sector wrote:   
   >>>   
   >>>> I'm not too rsync wise yet   
   >>>   
   >>>   From the first script I ever wrote using rsync...   
   >>> # set -x   
   >   
   > ...   
   >   
   >>> #  --progress  For the terminally bored.   
   >>   
   >> I'm a control freak, when I stagger out of bed to   
   >> dump caffeine I want to see how far it got   
   >   
   > --progress  is way to verbose. IIRC it lists each and every file, so   
   > that possible error messages fly out of the screen and you never see   
   > them, unless you are full time watching the screen.   
      
   I find the command "script" handy for watching and logging what a script   
   is doing and doing post command analyses. The command "tee" can also be used.   
      
   Script example:   
      
       script -c "rsync whatever" rsync.log   
       if [ $? -ne 0 ] ; then   
         mail -s "APP_XX FAILURE:  rsync whatever failed" root < rsync.log   
         echo "aborted APP XX"   
         exit 1   
       fi   
      
       rm --force rsync.log   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)