[an error occurred while processing this directive]
Upgrading client from script
You can run the following script if you want to have it update your AFS client
automatically.
# (still testing script)You can then run the afs_version script to see that you are using the latest version of the AFS client. Otherwise you can upgrade the AFS client manually with the instructions below.
Replacing client files onto the local disk
Most of the client setup has already been done when it was initially installed.
All we need to do is replace a few client binaries and change a symbolic link.
First we want to back up the old version of the AFS client:
# mv /usr/vice/etc/afsd /usr/vice/etc/afsd.old # mv /usr/vice/etc/afsauthlib.so /usr/vice/etc/afsauthlib.so.old # mv /usr/vice/etc/afskauthlib.so /usr/vice/etc/afskauthlib.so.old # mv /usr/vice/etc/sgiload/libafs.* /usr/vice/etc/sgiload/libafs.*.old
Go to one of the following directories depending on your OS version.
# cd /afs/ncsa/sgi_62
# cd /afs/ncsa/sgi_63
# cd /afs/ncsa/sgi_64
# cd usr/afsws/root.client/usr/vice/etcWarning: Make sure you do not cd to /usr/afsws/root.client/usr/vice/etc above, (the / is in front of the usr) or else you could get the wrong versions of the binaries.
Now copy the new versions of the client binaries:
# cp afsd /usr/vice/etc/ # cp afsauthlib.so /usr/vice/etc/ # cp afskauthlib.so /usr/vice/etc/ # chmod 755 /usr/vice/etc/afs*We now want to copy the the mods to the kernel. So cd to the sgiload directory:
# cd sgiloadIf the machine you are installing AFS onto is a single processor machine, then copy the following files:
If the machine you are installing AFS onto is a multi-processor machine, then copy the following files:
We can test the following files and see if there are any differences. If so then we will want to replace the files with the latest copy.
# diff /usr/vice/etc/CellServDB /afs/ncsa/service/etc/CellServDB # diff /etc/init.d/afs /afs/ncsa/service/etc/rc/sgi_afs.rcIf there are differences on any of the above files then replace the local copy with the newer copy from AFS.
Replacing AFS binary paths
Now you need to change the path for accessing all of the afs binaries.
# mv /usr/afsws /usr/afsws.old # ln -s /afs/ncsa/(hw type)/usr/afsws /usr/afswsReplace (hw type) with the system type of the machine which was determined above (ie. /afs/ncsa/sgi_62/usr/afsws).
Rebooting to start new AFS client
At this point all binaries have been replaced and the links changed. So to
start the new AFS client you will need to reboot.
# reboot
Testing to see if the newest version of the
client is installed
You can run the following script which will tell you if you are running
the latest version of the AFS client:
# /afs/ncsa/common/bin/afs_version[an error occurred while processing this directive]