#91 closed defect (fixed)
>t>setup_volume_reloader.ec should tell user where to create sys_vols.dump
| Reported by: | Eric Swenson | Owned by: | Eric Swenson |
|---|---|---|---|
| Priority: | major | Milestone: | MR12.7 |
| Component: | Tools | Version: | MR12.6f |
| Keywords: | Cc: |
Description
Setting up the volume dump involves running >t>setup_volume_reloader.ec and, after creating sys_vols.dump, running >t>setup_volume_reloader_2.ec. However, while normally the sys_vols.dump segment should be located in >udd>Daemon>Volume_Dumper, for >t>setup_volume_reloader_2.ec to work correctly and not emit errors, the user should create sys_vols.dump in >ddd>volume_backup. >t>setup_volume_reloader_2.ec uses this sys_vols.dump (in running dummy volume dumps), and then copies this segment to >udd>Daemon>Volume_Dumper>sys_vols.dump and deletes the temporary one in >ddd>volume_backup.
t>setup_volume_reloader_2.ec depends on being run from >ddd>volume_backup, but does not do a "cwd". >t>setup_volume_reloader.ec does perform a cwd to this directory, but since the user is given control between part 1 and part 2, it is possible that the working directory might be changed by the user.
This MCR: https://s3.amazonaws.com/eswenson-multics/public/mcrs/MCR10043.pdf addresses this issue.