mar2000.tar
|
|
|
Listing 1: setup.ini file
#setup.ini
#get initial startup conditions for a particular cell
#server ip OR hostname.
#master port that this instance runs on
s_port=2111
#sleep time for the auxiliary (local app that tails the logs) server
sleep=1
#how many seconds back to read a log when initally loading it into client gui
db_buffer_time=30
log_pgm=C!/apps/balsa/prod/bin/balsa_tail.pl
#where to start looking for files & apps
dir_start=/
#for win
#dir_start=C!/
# these are the paths to the associated LogViewer jobs.
# formats are
# win32
# aux_pgm=C!/apps...
# unix
# aux_pgm=/apps/...
#
#this allows use of ../ipcs/aux_lock to run only one aux svr per instance
use_aux_lock=0
#I recc just using a ps -ef | grep aux script instead, as this is
#prone to not working.
# the working temp dir for LogViewer.
local_temp=/export/home/greycat/prod/tmp
#how long ( in sec ) to run master server before cycling
# A good rule of thumb here is to run this so that when the master dies,
# cron then runs db_maint, and then
# the cron attempts to restart the master (note below on this).
# The aux_servers will wait 2 minutes before failing, so if you
# can cycle the master in under 2 minutes, the app (sans client gui)
# should stay functional.
# Note: you can attempt to start the master process every minute.
# if one is already running, another will NOT start.
# This does NOT apply for aux or clients!!!
master_kill_time=3520
#desktop cfgs will be overriden by users profile settings
desktop1=alpha
desktop1_color=yellow
desktop2=beta
desktop2_color=red
desktop3=gamma
desktop3_color=green
#note. it is recc that desktop 4 always be called something
# similiar to admin, as it is the administrative desktop for
# the app
desktop4=admin
desktop4_color=yellow
#Note. to setup a user profile, put a readable file under the dir
# ../profiles, named the users login name.
#how wide to make each log window in the gui
col_width=50
#
# the stuff that should point at your master server goes here
#
#this is where the root of LogViewer is at.
source_dir=/export/home/greycat/balsa2
#this is the ftp path the user must take to get to the cfg and db dirs
ftp_source_dir=/export/home/greycat/balsa2
#this is the master server ip address, it goes with the var s_port above
server=24.6.30.3
#for windows users, without exec files, you need to add
#the path to the perl.exe application, like so:
master_pgm_root=C!/apps/perl/bin/perl.exe
#also, for windows users, note these example paths should be changed to
#show correct windows path formats, substituting ! for :, ie: C:/ =>C!/
#YES, use /, not \ even on windows.
#these are the paths to the app files.
master_pgm=/export/home/greycat/balsa2/bin/balsa_master.pl
#kill master based on master_kill_time
master_pgm_timer=/export/home/greycat/balsa2/bin/balsa_cycle_master.pl
aux_pgm=/export/home/greycat/balsa2/bin/balsa_aux.pl
#this can be ran (if aux and master are up on the master node) by touching
# the file ../ipcs/master_maint on the node where the master resides.
dbmaint_pgm=/export/home/greycat/balsa2/bin/balsa_dbtrunc.pl
#this is very handy to have. only monitors 1 file at a time
# and if the file is del or truncates, you must restart this.
log_pgm=/export/home/greycat/balsa2/bin/balsa_tail.pl
#the api offers 3 things:
# -h for help
# -r to kill the master server.
# -i for the api to a client.
api_pgm=/export/home/greycat/balsa2/bin/balsa_api.pl
#these are with the production version and are used in blding the
#console application.
filter_pgm=/export/home/greycat/balsa2/bin/balsa_filter_bldr.pl
sub_pgm=/export/home/greycat/balsa2/bin/balsa_sub_bldr.pl
cli_pgm=/export/home/greycat/balsa2/bin/balsa_client.pl
lic_pgm=/export/home/greycat/balsa2/bin/balsa_license.pl
#
#-------------------------------------------------------------------------
#
# all data below this line is generated after running ../bin/balsa_install.pl
# please review it and edit accordingly to reflect (as applicable) the
# demo info above.
#
| |