Closed GoogleCodeExporter closed 9 years ago
Do you mean initial startup or while normal operation?
Original comment by axk...@gmail.com
on 8 Sep 2010 at 5:40
I actually meant during normal operation, but I guess the same kind of
reporting could also be valid for initial startup - but I thought the initial
sync was just handed off as a single operation? If that's the case then just
normal operation is what would be really handy.
Thanks for the feedback.
Original comment by cfmshado...@gmail.com
on 8 Sep 2010 at 10:33
yes, inital startup is just one recursive rsync call.
An ETA is almost close to impossible. I could add a log message tough, how many
directory/file entries are left in the delay queue.
Are you syning the same directory tree to 6 targets at the same time? In that
case another change might be of far more importance to you. Currently lsyncd
waits for one rsync to finish before calling the next. It could however as well
without any harm to the internal logic call rsync for each target at the same
time in the case multiple targets are specified for one source branch. Depends
on where you bottleneck is. If it is your upstream, it wont help much, if it
isn't it would quite improve performance.
Original comment by axk...@gmail.com
on 8 Sep 2010 at 6:21
if you check the source in the subversion it now has a "--verbose" option, when
turned on, it well tell you on each action how many items are expired or
delayed. Depending on operation mode this are dirs or files.
Original comment by axk...@gmail.com
on 10 Sep 2010 at 7:17
Original comment by axk...@gmail.com
on 10 Sep 2010 at 7:17
Original comment by axk...@gmail.com
on 4 Oct 2010 at 8:30
Original issue reported on code.google.com by
cfmshado...@gmail.com
on 7 Sep 2010 at 8:57