>>
>> Has anyone created an automated procedure to update an afs client machines
>> memory after the information in the CellServDB has changed. Currently, we just
>> log onto the clients and issue an "fs newcell ..... ..... ....." command.
>>
>> --------------------------------------------------------------------------
>> _/ _/ _/_/_/ _/_/_/ _/_/_/ _/_/_/ Michael Ganzberger
>> _/_/ _/ _/ _/ _/ _/ _/ Lawrence Livermore Lab.
How quickly does this need to happen on all clients?
Is it OK to do it within 24 hours?
On most of our AFS clients, ROOT runs a daily cron job to update the
local CellServDB whenever the master copy is changed. The script looks
like this:
%% cat /afs/nersc.gov/admin/bin/syncupdate
#
# Script to update the CellServDB file from the master if it
# has changed.
#
diff /usr/vice/etc/CellServDB /afs/nersc.gov/service/CellServDB > /dev/null
if [ $? -ne 0 ]
then
/bin/cp /afs/nersc.gov/service/CellServDB /usr/vice/etc/CellServDB
fi
#--------------------------------------------------------------------------------
The FIX is to insert another line after the /bin/cp command:
/afs/nersc.gov/service/Run_fs_newcell
When the AFS Admin person updates the master CellServDB file, the
Run_fs_newcell script is also updated to include an "fs newcell"
command for those cells which now have different servers.
Both files are in the same AFS volume so they are released together.
Each client system will be updated within 24 hours.
----------------------------------------------------------------
| Joe Ramus NERSC Livermore (510) 423-8917 [EMAIL PROTECTED] |
----------------------------------------------------------------
