Shell Programming and Scripting

Hello

i am working on a project here is part of script that i need a help in

get process SpectroSERVER current size if it exceed 3850 MB then
#pkill -TERM ArchMgr
and wait to succfull shutdown message from the log file to proceed to the next step
#tail -f $SPECROOT/SS/DDM/ARCHMGR.OUT
ArchMgr has successfully shut down
if got above message then
# pkill -TERM SpectroSERVER
and wait to succfull shutdown message from the log file to proceed to the next step
#tail -f $SPECROOT/SS/VNM.OUT
SpectroSERVER has successfully shut down
if got above message then proceed to next step

What do you mean by that?
That if the process's resident set size, or virtual size, of it alone,
or including all its children, or those belonging to the same process group etc. exceed this threshold of memory.
What about memory mapped pages or shared memory,
reserved or even used pages on swap?

hello when do top i got the following
PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND
19202 specadm 29 42 0 3497M 3222M sleep 42.8H 0.00% SpectroSERVER

i need script to check the SIZE if it is > 3850 to proceed

Ah, you were reading top's output.
Then I gather the proc's resident set size is meant,
roughly what the proc used from physical memory.
For that to get you could run a ps command.
Do we know the proc's PID beforehand (maybe from some pid file),
or do we need to parse the proc table first?
Assumed we knew the PID you could run

Code:

$ ps -p <PID> -o rss=

Depends on the ps/OS; on Linux this number should be in KB.
Other ps return number of memory pages.
If you want to check it on a regular basis
you could set up a cronjob which checks every 5 mins or so.
Even better yet would be a monitoring solution like Nagios
(but maybe overkill?)
From the Nagios Plugins you could set up a check command
involving the check_procs plugin.

allright this can be a good start ,, what about rest of the script ?

regards

Hello have created script like follwoing ,,, thanks anybody to check and advice

set a=3800000
if [ $a -lt'ps -p `pgrep SpectroSERVER` -o rss=' ]
then
pkill -TERM ArchMgr
b= tail -f $SPECROOT/SS/DDM/ARCHMGR.OUT | grep "ArchMgr has successfully shut down"
if [ $b ='ArchMgr has successfully shut down' ];
then
pkill -TERM SpectroSERVER
fi
c= tail -f $SPECROOT/SS/VNM.OUT | grep "SpectroSERVER has successfully shut down"
if [ $c ="SpectroSERVER has successfully shut down" ]
then sudo /opt/spectrum/lib/SDPM/processd.pl stop
fi
if [ `pgrep processd`]
then pkill processd
fi
procs2kill="LocServer NSAgent telnetd osagent VnmShd"
for proc in `echo $procs2kill`
do
pkill $proc
done
sudo /opt/spectrum/lib/SDPM/processd.pl start
. /home/specadm/spectrum_env ; $SPECROOT/bin/launchinstdbapp `/usr/bin/hostname` SS n VNM.OUT
x= tail -f $SPECROOT/SS/VNM.OUT | grep "is now ready on port 0xbeef..."
if [ $c ="is now ready on port 0xbeef..." ]
then . /home/specadm/spectrum_env ; $SPECROOT/bin/launchinstdbapp `/usr/bin/hostname` ARCHMGR y ARCHMGR.OUT
fi

If the script you came up with is working for you
then it's quite ok.
But because you asked maybe just some suggestions
(although this is probably only a matter of personal taste)
I think here you mixed up single quotes (embracing the whole ps command)
with backticks.
Though it may look daft it is quite ok to have nested backticks.
Nevertheless, I am not particularly fond of backticks because they have become obsolete in modern posix shells,
and thus their use is deprecated.
With bash, ksh, zsh, hp-ux sh etc. you should use $(...) instead.
So this would be how I would rewrite it

Code:

if (( $a < $(ps -p $(pgrep SpectroSERVER) -o rss=)) )); then

But this is still quite ugly.
With all those pairs of parens one easily could lose counting the closing ones.
So better split it up into several statements.
Also, what if the inner cmd expansion of pgrep fails?
Also, as you are going to calculate with these vars
you should better declare them as integers.
Also better use meaningful, imaginative variable names
Maybe one could rewrite it this way?

Code:

declare -i RSS_THRESHOLD=3942400
spectro_pid=$(pgrep SpectroSERVER)  # does its cmd name really appear in mixed case in the proc table?
[[ -z $spectro_pid ]] && exit 1
declare -i spectro_rss=$(ps -p $spectro_pid -o rss=)
if (( RSS_THRESHOLD < spectro_pid )); then

On the other hand you could parse the RSS in one proc table lookup like so

Code:

spectro_name=SpectroServer
set -- $(ps -e -o pid,ppid,rss,comm|awk -v pn=$spectro_name '$4~pn&&$2==1{print$1,$3}')
declare -i spectro_pid=$1 spectro_rss=$2

Yet another variant was to retrieve the RSS from the procfs like

Code:

spectro_rss=$(awk '$1~/^VmRSS:/{print$2}' $(printf /proc/%lu/status $(pgrep -P1 $spectro_name)))

These shall only serve as examples that there is more than one way to do it
(viz. TIMTOWTDI, spoken "timtowdy" as the Perl hailers use to say)
It's not clear to me how this should work
since it ought to produce a syntax error
though I think I can gather what the intension is;
viz. tail on the log until a certain expression appears
and then assign this line to variable b, right?