Old slices weren't having their totals cary over when NM was reset or reinstalled...
authorFaiyaz Ahmed <faiyaza@cs.princeton.edu>
Wed, 25 Apr 2007 22:19:59 +0000 (22:19 +0000)
committerFaiyaz Ahmed <faiyaza@cs.princeton.edu>
Wed, 25 Apr 2007 22:19:59 +0000 (22:19 +0000)
commit3cd8f8fd2189939bfeee4902acfd761d065a0a43
treea875de74bf5999dcce2e59c24aef3edad604cfd3
parent2aec8ca40fbf52b8b75ceee972781ed73cd0d432
Old slices weren't having their totals cary over when NM was reset or reinstalled.  New slices would start out with 0 bytes in their byte counts, then when update was called 10 minutes later, their running byte count would would already be over their max, then the slice would get capped.  New slices that are already running (presumably from a previous instance of NM), should have their byte counts carried over on init.
bwmon.py