Closed bmeagherix closed 9 months ago
Hmmm. Seems like the fix may be breaking something else. Let me see if I can rectify.
Hmmm. Seems like the fix may be breaking something else. Let me see if I can rectify.
OK, adding a check vs copy_manager
resolved that issue. (FWIW, scstadmin
already checks against it in multiple other locations.)
Hi Brian,
Thank you for the patch!
Thanks, Gleb
When running scstadmin to load a config file with a reduced the number of targets defined, the first time will generate an error
Use of uninitialized value in numeric ne (!=) at /usr/local/sbin/scstadmin line 2834.
Rectify by checking for the uninitialized value, and taking appropriate steps (i.e disable the target).It appears that the first time the command is run the target is supposed to get disabled, and fully removed when next run.
Here is an example of a failure when switching from 2 targets to 1 target (demonstrates error, target not properly disabled):
and here is the same change steps executed with the updated
scstadmin
script (no error):