topic Re: script quries in Operating System - HP-UX

script quries

yc_2 — Mon, 27 Jun 2005 20:47:26 GMT

Hi,

When I run a script, I got the following using ps -ef | grep <script>:

cis_opr 11610 1 0 08:35:30 ? 0:00 /bin/ksh ./<script>

Can the script be run so that ps -ef | grep <script> will get the following (ie without /bin/ksh>

cis_opr 11610 1 0 08:35:30 ? 0:00 ./ezproxy

Thanks in advance.

Re: script quries

Matthew_50 — Mon, 27 Jun 2005 21:18:35 GMT

you have to use awk to parse the output,
for example,

ps -ef | grep <script>|awk '{print $1,$2,$3,$4,$5,$6,$7,$9}'

Re: script quries

Patrick Wallek — Mon, 27 Jun 2005 22:56:00 GMT

How are you running the script?

Are you running it like:

$ ksh ./scriptname

or do you have #!/usr/bin/ksh as the first line of the script?

Re: script quries

yc_2 — Tue, 28 Jun 2005 00:52:53 GMT

Hi Patrick Wallek,

When the script was executed, it consists of the following:
#!/usr/bin/ksh

I cotook out the #!/usr/bin/ksh and ran:

#ksh ./<script>

The result of ps -ef | grep <script> is the same.

Re: script quries

MarkSyder — Tue, 28 Jun 2005 02:48:02 GMT

If you are running ksh script, that suggests the script is not an executable.

Try:

chmod +x script (or chmod 744 if you only want the owner to be able to execute the script)
./script

Mark Syder (like the drink but spelt different)

Re: script quries

Vibhor Kumar Agarwal — Tue, 28 Jun 2005 03:32:26 GMT

I think the problem is that the script that you are running has some syntaxes specific to ksh.

That's why you have to use either of the 2 things: ksh or #/usr/bin/ksh

and this may be the reason why its showing in ps -ef.

Check what is your default shell, try changing it and then running.

Re: script quries

Ralph Grothe — Tue, 28 Jun 2005 04:01:15 GMT

I'm afraid, I think you will have to parse the output from ps yourself.
It's true that if you run a script in the process table as cmd appears the interpreter (i.e. in your case /bin/ksh).
Because I haven't your process running I used a running Perl script of mine as an example for how such parsing could look like.
As you may recognise I stripped off the 2nd field from the right side which holds the interpreter.
I used Perl for parsing but you could as well use any combination of awk, grep, sed, cut, tr ...

$ UNIX95= ps -fC arschd|perl -anle 'if($.>1){$F[-2]=undef;print "@F" }'
saz 4288 1 0 Jun 26 ? 00:01 /usr/local/sbin/arschd

I have to admid, because with ps output you have varying fields, that it would be better to use Perl's pack() function for this purpose.
But I thought this would be too distracting.

Re: script quries

Stuart Browne — Tue, 28 Jun 2005 08:52:05 GMT

An expansion on Mark Syder's answer.

Yes, make the script file it's self executable (chmod), but also make sure that the first line of the script is something similar to:

#!/bin/ksh

This will tell the OS that when you run the script directly (i.e. ./ezproxy), it will use the interpreter '/bin/ksh' to run it in.

Go #! magic ;)