From morrison@sxt3.space.lockheed.com Fri Jun 7 02:06:45 1996 Date: Thu, 6 Jun 1996 23:06:25 -0700 From: morrison@sxt3.space.lockheed.com (Mons D. Morrison) To: mdi@mdisas.nascom.nasa.gov Subject: Guidelines on making changes to /mdisw Rules for Making Changes to the /mdisw Tree Contents ==================================================== Ver 1.0 MDM 6-Jun-96 * FUNDAMENTALS The list of directories and whether there is a master site or not is located in the file: /mdisw/mirror/mdisw_distrib.tab If the directory branch says "NONE", then the latest version is taken from any of the 4 sites. * DELETING Since several of the /mdisw directories have no master machine, the latest files are taken from all of the different machines. As such, if you delete a file on a single node, it could very well be copied back into place within 24 hours. There is a script which should be run from mdisas as user "mdi" (or as yourself if you have .rhost files on mdisas, quake, diapason, and mdibbs). A sample command is: rm_all_mdisw /mdisw/doc/victoria.joe NOTE: You must include the path in the command. * MOVING FILES AROUND Because of the same problem talked about under DELETING, care needs to be taken when moving files around. I guess I'd recommend that 1. Choose a site which has the latest files you want to move around 2. Move the files around 3. Delete the files from their OLD location following the procedure described in the "DELETING" section. * ADDING AND MODIFYING FILES Generally, files should not be edited directly in the /mdisw tree. They should generally be copied out to a private working area, edited and put back on-line. Editing the files directly in the /mdisw can cause a variety of problems. (a) an editors "auto-save" can write the file out before you are finished, (b) you may have introduced an error, so full debugging should be done off-line, (c) some editors leave annoying backup copies of the files. Some techniques for putting files online are: "msput" - for files in /mdisw/doc, /mdisw/idl, /mdisw/bin "cp -p" - for files in /mdisw/setup "freeze"- for files in /mdisw/cfl/prep "certify"-for files in /mdisw/cfl/flight If you must copy files from /mdisw to /mdisw_cmd, you must use the "-p" option. Someone copied the full contents of /mdisw/bin on 30-Jan and it makes determining the master site for the files difficult. Changing files in the /mdisw/setup directory must be done with great care. It can cause things to stop working very quickly if it is not done properly. * SAVING COPIES OF FILES Several of us are very good at saving copies of files before we edit them. Unfortunately, this can leave a ton of junk in the directories. For example: versions.pl and versions.pl.prev or idl_batch_run.pro and idl_batch_run.pro0 I'd like to request that people use the command "msback" to make a copy of their file in the /mdisw/save_copy directory. A sample command is msback filename This will keep the contents of the /mdisw tree relatively clean and uncluttered. * UPDATING MDICMD The procedure is TBD * SETTING DIRECTORY AND FILE OWNERSHIP AND PROTECTION It may be necessary to run a script to make sure that all of the directories have the proper protection (group must be mdi and protection must be 775). Some egse files must be owned by root and have the "sticky" bit set. The procedure is to log in as root and to execute the file: TBD