topic Re: ps: option in Operating System - HP-UX

ps: option

P-Dicky — Tue, 09 Jun 2009 13:36:00 GMT

Good Morning,

Hoping this is a simple fix not a scripting guy.. Here is the error I am getting.

# ./startwrx

Starting WRX System.

Give it some time Starting up WRX
ps: option requires an argument -- u
usage: ps [-edaxzflP] [-u ulist] [-g glist] [-p plist] [-t tlist] [-R prmgroup] [-Z psetidlist]
line
usage: kill [ -signo ] pid ...
[root:testomni:/usr2/amv/cmd]
#

Re: ps: option

Patrick Wallek — Tue, 09 Jun 2009 13:40:21 GMT

The '-u' option requires either a numeric UID or a userid as an option.

The script you attached says it is doing a 'ps -u ${PROJECT_NAME}....' but I do not see the ${PROJECT_NAME} defined in the first few lines of the script.

You need to get that variable defined appropriately before the script will work.

Re: ps: option

Mel Burslan — Tue, 09 Jun 2009 13:43:59 GMT

In your attached script, there is a reference to a environment variable called PROJECT_NAME and it is not defined. Your ps command is complaining about this null variable as the -u option requires this variable to be set.

Re: ps: option

James R. Ferguson — Tue, 09 Jun 2009 13:44:11 GMT

Hi:

Most notably, the variables 'PROJECT_NAME' and 'PROJECT_DIR' are never set. This cause the usage error you get.

A useful protection against chasing things like this is to begin you script like:

#!/usr/bin/ksh
set -u
...

Regards!

...JRF...

Re: ps: option

P-Dicky — Tue, 09 Jun 2009 14:11:12 GMT

Sorry ${PROJECT_NAME} was not set... They are both set in .profiles

I have corrected this but I'm now stuck at this

# ./startwrx

Starting WRX System.

Give it some time Starting up WRX
line

Re: ps: option

Mel Burslan — Tue, 09 Jun 2009 14:21:31 GMT

Since the line you said you are stuck at, is not in the script itself, I am under the impression that your application is spitting this message. Without knowing what this executable located at ${PROJECT_DIR}/amv/bin/utdbu is, it is almost impossible to say why you are stuck at this point.

If you have support agreement with the vendor of this software, I'd strongly suggest contacting them.

Re: ps: option

Patrick Wallek — Tue, 09 Jun 2009 14:44:28 GMT

>>Give it some time Starting up WRX

>>Since the line you said you are stuck at, is not in the script itself,

Actually, it is.

Here's the section of the script that's causing the delay....

while [ "$systat" -ne "START" ]
do
if [ "$firsttime" != "TRUE" ]; then
if [ $waittime -le 0 ]; then
echo " Unable to Start WRX System! " 1>&2
exit 1
fi

# wait for a bit
sleep $sleeptime
waittime=`expr $waittime - 1`
fi

firsttime="FALSE"

echo "gc\nf\n2\n\nq\nq\n" | ${PROJECT_DIR}/amv/bin/utdbu |
while read line
do
firstarg=`echo $line | awk '{print $1}'`
if [ "$firstarg" = "cnflng" ]; then
systat=`echo $line | awk '{print $4}'`
fi
done
done

It appears that this attempts to start whatever this is. It gets the status of the process via the 'systat=' line above. If systat is not equal to START, then it will wait and try again. Each time through the script the "waittime" is decremented by 1. So, it will run through the script '90' times, sleeping 10 seconds each time (if I am figuring correctly), so you have a potential delay of 900 seconds (15 minutes) if the system is not starting correctly.

Re: ps: option

Tarun Kumra — Wed, 10 Jun 2009 02:45:02 GMT

As said by Patrick and Mark, you will need to assign some value to the variable PROJECT_NAME.

Regards
Tarun

Re: ps: option

P-Dicky — Wed, 10 Jun 2009 10:32:19 GMT

Starting to make sense thank you all.

Re: ps: option

P-Dicky — Wed, 10 Jun 2009 10:33:57 GMT

Close, reply... So close. Thanks Again