July 24, 2002
NO CHANGES TO ANY CONFIGURATION FILES SHOULD BE MADE DIRECTLY IN
ANY STATION BUILT BY STRING MASTER. THIS INCLUDES ALL
station.cfg FILES AS WELL AS ALL OTHER .cfg FILE. Changes should
only be made via String Master.
In its first use, tk_pwbox.pl is being used with RELEASE_JOB_NOW
and EXPIRE_CURRENT_TIMERS in the Gran Find station. When an
operator clicks on the RELEASE JOB NOW or the EXPIRE CURRENT
TIMERS buttons in the GUI, he/she is prompted for a password
before the job is released. An incorrect password results in the
job not being released.
Trigger PGE jobs will fail if the trigger data type turns up
missing. This, of course, should never happen. One way this can
happen is if, after a job gets through Gran Find, someone manually
cleans out or manually deletes the trigger data type. It can't be
deleted by clean_expired_data.pl since Gran Find does a /touch/ on
granules it locates to ensure that they stick around a while longer.
Data that is cleaned by virture of the clean_expired_data.pl
script now produce clean data work orders with CLEAN_EXPIRED in
the file name. In this way, such data cleans can be easily
distinguished among the archived logs.
Lifeguard has been replaced by Smart Alloc, a new GUI for viewing
the current state of the disk pools. It should prove more useful
and it addresses some of the shortcomings of Lifeguard.
Detailed File Changes
New GUI replacement for Lifeguard that provides a graphical
monitor for the Allocate Disk database, which shows the available
space in the data pools. For each pool, it shows how much of the
pool has been allocated in terms of granules. There is both a
bar-type graphical display, as well as the actual numbers of
granules used (allocated), left (space available), and total. The
color of the bar turns yellow at 70% used, orange at 85% and red
Got rid of any checking for the grancentral.csv file and thereby
fixed a bug where this file was being created anew each time
database clean up was run.
Modified Integrity Check portion so that if the audit_config.pl
script is not found, the program quietly skips it and doesn't flag
it as an error. With String Master coming, the audit_config.pl is
Changed the output work order file name to something that includes
'EXPIRED' so that when the Clean Data log files are archived, one
can distinguish this type from other types (e.g. manual clean out
of data via the Clean Data GUI).
Fixed a bug where the script was still looking for the
granfind.cfg file in order to know directory locations of data.
This information is gotten from the allocdisk.cfg file instead.
Stringmaster can be run in 5 different modes:
1. Query mode (-q argument)
Queries the current configuration for a string
Example: stringmaster.pl -q tmp.1 -s S4PM10_TE_FW.cfg
puts the configuration of the S4PM10_TE_FW string in the directory
2. Update mode (-u argument)
Updates the current configuration for a string
Example: stringmaster.pl -u -s S4PM10_TE_FW.cfg
Overwrites the current configuration files in the S4PM10_TE_FW string.
3. Creation mode (-c argument)
This creates a new string, or updates an existing one. It is the
only way to update a string if new directories or symbolic links
Example: stringmaster.pl -u -s S4PM99_TE_FW.cfg
Creates a new configuration for the S4PM99_TE_FW string.
4. Append mode (-a argument)
This appends any max_children override values to the station configuration files as $cfg_max_children values.
Example: stringmaster.pl -a -s S4PM10_TE_FW.cfg
5. Hypothetical mode (no arguments)
This creates the temporary configuration files that would be used for an
update or creation.
Example: stringmaster.pl -s S4PM10_TE_FW.cfg
Puts new configuration files in ./tmp.
More details can be found in the stringmaster and related man pages.