Now my question is: is there anything in
rdiff-backup itself that could explain this? Some part of the script that
still runs after the stats are printed and that could suffer big delays?
If that's not it, then we clearly need to look into our I/O, possibly our
write cache, but I'd like to eliminate the easy possibilities first.
Thanks in advance
Laurent De Buyst
ICT - System Administrator
[Prev in Thread]
[Next in Thread]
[rdiff-backup-users] Delay between EndTime and process end,
Laurent De Buyst<=