C - I've taken classes for it, never used it much.
On the other hand, I use shell scripting, every day. I use the techniques even on the command line. For instance:
Say you have a volume group that has 30 logical volumes in it. You want to unmount the logical volumes and deactivate the volume group.
A SA that canâ t script, might umount the first logical volume, then recall the command, edit the line for the second logical volume, then execute the command. This SA would then repeat the process for all 30 logical volumes. This is a lot of typing, and takes quite a while.
A SA that is familiar with scripting could do the following all from the command line:
for lv in `bdf | grep vgXX | awk '{print $6}'
do
print ${lv}
umount ${lv}
done
Now, you might say what if some of the logical volumes are mounted to mount points that reside within other logical volumes of the same volume group, you would want to make sure that they get unmounted in the correct order. Well, with the above command line script, any LV that is â busyâ will not get unmounted. So, all you have to do is recall the previous command, and execute it again. If there is a file system that is busy because of another reason, then fix that problem and again recall the previous command and execute it.
As you can see, you donâ t even have to type a single mount point in order to get all of the LVâ s unmounted. This method can be accomplished in a matter of seconds. You can then issue the vgchange command.
I normally type something like the above command line script leaving out the umount command. After making sure that the result shows the correct logical volumes, I simply recall the command, press â vâ to edit the command line in vi (another necessity to be familiar with) and insert the umount command in the correct location.
Yes, a SA can do the job without using shell scripting, but that SA will not be
In a world without fences, who needs Gates?
