When setting up the crank for the first time, an out_of_bounds condition is raised

[Eric Swenson]

In order to set up the crank on a new system, you have to follow several steps (another ticket will address how to improve that). The final step is to actually "run" the crank for the first time. This is done by issuing this command:

cwd >udd>sa>a
ec master crank

While this does the trick (schedules the crank for a later time) and results in a successful crank run when the crank absentee process later runs, you get the following error on the terminal:

truncate: Entry not found. meter_data.print
truncate: Entry not found. bwchart.print

Error:  out_of_bounds at b_and_w$|2253
(>system_library_tools>bound_admin_rtnes_)
referencing >udd>sa>a>today.use_totals|776004
Attempt to access beyond end of segment.
r 07:36 8.176 1047 level 2

This is presumably due to not correctly handling the case where the crank is run the first time. We should clean this up.

[Eric Swenson]

This issue occurred because of a bug in disk_usage_stat, which was fixed in MR12.8-1006. The fix was described in ​https://s3.amazonaws.com/eswenson-multics/public/mcrs/MCR10097.pdf.