topic unix scripting - understanding read_param in Operating System - HP-UX

unix scripting - understanding read_param

Derek Brown — Tue, 27 Mar 2007 06:39:43 GMT

Please see the attached unix script. It copies oracle redo logs from our production machine to the contingency machine every 15 minutes.

My boss has asked me to look at it and understand it as I may soon have to support it. I've done some shell scripting in the past so I'm not a novice; having said that I'm no expert either.

The script makes use of something called 'read_param'. My question is this : what is read_param and where is it defined ? By putting set -x at the start of the script I can see that it does what it says on the tin i.e. it reads a parameter. I can see that it reads the value of LOGHOME (for example) as /var/alexbkup. Fair enough, but I've looked until I'm blue in the face to find where read_param is defined. This is where I've looked so far :

Is it a unix command ?
/etc/profile
$HOME/.profile
aliases
$HOME/.kshrc
Variables within the script
Functions within the script

I can't see it defined anywhere. My guess is I'm missing something really obvious. If any of you guys can help I'd be most appreciative. Thanks

Re: unix scripting - understanding read_param

Peter Godron — Tue, 27 Mar 2007 06:46:36 GMT

Hi,
there seem to be some sort of eval equivalent going on.

Search in your PATH:
"/bin:/usr/bin:/usr/local/bin:/opt/backups/bin"

Re: unix scripting - understanding read_param

James R. Ferguson — Tue, 27 Mar 2007 06:51:10 GMT

Hi Derek:

Your 'read_param' is an external script or binary that returns a value to the calling script.

For example:

LIMIT=$(read_param FS_THRESHOLD)

...set the value of LIMIT to whatever 'read_param' makes it based on the key FS_THRESHOLD.

It would be clearer and much cleaner (security-wise) if the references were made with an absolute path rather than relying on "." being in the user's path.

Regards!

...JRF...

Re: unix scripting - understanding read_param

Peter Nikitka — Tue, 27 Mar 2007 08:26:41 GMT

Hi,

since '.' is NOT in the PATH set by the script:
export PATH="/bin:/usr/bin:/usr/local/bin:/opt/backups/bin"

... and is not a std-command either, you'll have to look into
/usr/local/bin
/opt/backups/bin
for file called 'read_param'.

mfG Peter

Re: unix scripting - understanding read_param

James R. Ferguson — Tue, 27 Mar 2007 09:00:09 GMT

Hi (again):

> Peter N. wrote: since '.' is NOT in the PATH set by the script:

Yes, I totally missed the fact the script sets its own PATH as opposed to inheriting it. In fact, this is good technique. Examine the directories Peter noted for the 'read_param' entity.

Regards!

...JRF...

Re: unix scripting - understanding read_param

Derek Brown — Tue, 27 Mar 2007 09:38:03 GMT

Thanks guys. Problems solved now.
I want a kick up the behind for not spotting this myself. read_param was simply a script in /opt/backups/bin

Re: unix scripting - understanding read_param

Dennis Handly — Tue, 27 Mar 2007 23:35:21 GMT

>I want a kick up the behind for not spotting this myself.

If you do a "whence -v", it will tell you what the shell thinks it is.