topic Re: Korn scripting question in Operating System - HP-UX

Korn scripting question

u856100 — Fri, 27 Oct 2006 03:09:08 GMT

Hi All,

I'm trying to run the following ....

$ script test.scr
$ ls -1 *.txt
$ exit
$ cat test.scr

... but inside a korn script. So something like :

#/usr/bin/ksh
script test.scr << EOF
ls -1 *.txt
exit
EOF
cat test.scr

This obviously will not work, but does anyone know how I can pass an exit statement to the script process in order for it to terminate?
The script is more complicated than the above (in case someone asks why I'm using the 'script' binary), but I cannot redirect the following to a file :

find /app/oracle/admin/udlgrid1/udump -name "*.trc" -mtime 2 -exec /usr/sbin/fuser {} \; | grep : | awk -F":" '{print $2;next}'

my attempt using :
find /app/oracle/admin/udlgrid1/udump -name "*.trc" -mtime 2 -exec /usr/sbin/fuser {} \; | grep : | awk -F":" '{print $2;next}' > tracefiles.txt

does not seem to work

any other options appreciated

thanks in advance
John

Re: Korn scripting question

Steven E. Protter — Fri, 27 Oct 2006 04:58:32 GMT

Shalom John,

I would suggest building a two script system with an exit at the end of the second script.

SEP

Re: Korn scripting question

Ralph Grothe — Fri, 27 Oct 2006 06:13:55 GMT

If I remember correctly, if you only require the PIDs of "active" files then you need to redirect stderr of the HP-UX incarnation of the fuser command to /dev/null.
Try appending 2>/dev/null before piping into grep or awk.
I'm not quite sure if I got what your intentions are?

Re: Korn scripting question

spex — Fri, 27 Oct 2006 07:19:42 GMT

John,

I'm also not sure of your intentions. Oracle trace files are generated when a background process or user process encounters an exception. I don't see why any process would have a trace file open after it has been written to initially.

In any event, you may want to give 'lsof' a shot, although I personally find it very flaky under HP-UX.

By the way, the format of a background trace filename is:

sid_proc_ospid.trc

where
sid = Oracle instance name
proc = Oracle bg thread name
ospid = HP-UX pid

As you can see, the pid of the offending process is embedded in the filename. This is also true for user thread trace files, although the naming format is a bit different.

PCS

Re: Korn scripting question

u856100 — Fri, 27 Oct 2006 07:29:59 GMT

thanks people, appreciate the responses. We have some problems with oracle not releasing file handles on trace files (very strange). As a result our housekeeping scripts are creating a load of zombie processes that are still claiming space.

I'll go with the two script option

many thanks again

Re: Korn scripting question

rariasn — Fri, 27 Oct 2006 07:41:52 GMT

Hi Joh,

Use the "exec" command rather "script"

Sample:

# begin script
exec > /tmp/sample.txt
find /app/oracle/admin/....
...
# end escript

rgs,

Re: Korn scripting question

Peter Nikitka — Fri, 27 Oct 2006 10:20:22 GMT

Hi,

if you want to have the stderr as well in the file - what I assume - modify the solution of rgs to:

exec >/tmp/listing 2>&1
commands...

mfG Peter

Re: Korn scripting question

Arturo Galbiati — Mon, 30 Oct 2006 02:52:47 GMT

Hi,
you could use the '{}' way:

#/usr/bin/ksh
{
ls -1 *.txt
exit
} >test.src
cat test.scr

HTH,
Art