christos@zoulas.com (Christos Zoulas)  wrote:
 > >[grok hpeyerl 9 ]; !!
 > >ps -ax | grep rsync
 > > 8707 p5 S+    0:24.94 rsync -vaxH . /backup/home/ 
 > > 8708 p5 S+    0:23.53 rsync -vaxH . /backup/home/ 
 > > 8709 p5 S+    0:20.99 rsync -vaxH . /backup/home/ 
 > >
 > >
 > >You'll note the conspicuous lack of any sort of progress over 
 > >the space of a minute.  It does accrue cpu usage over the
 > >progress of time but isn't actually accomplishing anything. A
 > >'ktrace -p' shows it's just doing this:
 > >
 > >  8707 rsync    CALL  gettimeofday(0xbfbfd8ac,0)
 > >  8707 rsync    RET   gettimeofday 0
 > >  8707 rsync    CALL  gettimeofday(0xbfbfd8a4,0)
 > >  8707 rsync    RET   gettimeofday 0
 > >  8707 rsync    CALL  select(0,0,0,0,0xbfbfd89c)
 > >  8707 rsync    RET   select 0
 > >  8707 rsync    CALL  gettimeofday(0xbfbfd8a4,0)
 > >  8707 rsync    RET   gettimeofday 0
 > >  8707 rsync    CALL  wait4(0x2204,0xbfbfd8e4,0x1,0)
 > 
 > Ok, that is the parent waiting for the child to finish
 > In this case pid 0x2204 = 8708. What is the child doing,
 > and not finishing?

Pretty much nothing:

 8707 p5 S+    0:40.09 rsync -vaxH . /backup/home/ 
 8708 p5 S+    0:23.53 rsync -vaxH . /backup/home/ 
 8709 p5 S+    0:20.99 rsync -vaxH . /backup/home/ 


  8708 rsync    EMUL  "netbsd"
  8708 rsync    CALL  select(0x2,0,0xbfbfc048,0,0xbfbfc020)
  8708 rsync    RET   select 0
  8708 rsync    CALL  select(0x2,0,0xbfbfc048,0,0xbfbfc020)


It's still all running. It has copied no more new files, it hasn't
reported anything, and as you can see, hasn't really accrued all
that much more cpu time.