UNIX for Dummies Questions & Answers

I am trying to write a one line command for Oracle grid control. I am using a semi-colon to separate the commands. But, I am having a problem with a shell script accepting input. Wondering if you can help.

Here is what I am trying to do:

(PGPRD5432)@prd01:/> cd /export/home/postgres ## home directory, currently work on (PGPRD5432)
(PGPRD5432)@prd01:~> source .bash_profile## script that allows me to choose environment variables

Multiple Postgres Clusters, Please Select One
(PG: Env Name: Port: Version)

1) PG:PRD:5432:8.1.4
2) PG:PRD:5434:8.1.4
#? 2 ##Here, I enter option 2
(PGPRD5434)@prd01:~> env | grep PG ##Now changed to (PGPRD5434)
PGENV=PRD
PGBKUP=/pgbackup/PGPRD5434
PGCLUST=PGPRD5434
PGWORK=/pgwork
PGDATA=/pgcluster/data/PGPRD5434
PGVERSION=8.1.4
(PGPRD5434)@prd01:~>

When I try a one liner, I cannot figure out how to get .bash_profile to accept the "2". Here is what I am trying with no success.

cd /export/home/postgres;. .bash_profile | 2; env | grep PG

cd /export/home/postgres;. .bash_profile; 2; env | grep PG

cd /export/home/postgres;. .bash_profile; echo "2" ; env | grep PG

cd /export/home/postgres;. .bash_profile; echo 2; env | grep PG

An interactive profile is highly evil. Do you absolutely _have_ to use this thing?

If so, try using echo and pipes to send the '2' to the source command:

Code:

echo "2" | . /export/home/postgres/.bash_profile ; env | grep PG

If the above doesn't work, you might need to use 'expect' to simulate a tty for the source command to interact with.

Really, find the person responsible for this mess and give them a smack in the head. A profile that pauses and waits for input is a great way to screw up all kinds of automation processes. At least change it to check if it's running interactive or not and make an automatic choice if not.

The .bash_profile is the script your running?

I bet that there is actually a script inside that login script that you could dissect that could do all of this cleaner. Its actually building a menu by probing the database environment and what not.

Thanks for trying to help. But the echo "2" didn't work either. However, the way you cleaned it up is awesome.

We approaching it differently. The .bash_profile script gives the option to set postgres clusters (ports). Instead of trying set my port. I am going to put the port in the command. Like this:

psql -p 5432 -c "select 'port: 5432', pg_postmaster_start_time();" | grep "[0-9]-[0-9]" | sed 's/^ //'


Another issue I had was that the Oracle grid control agent seems to do an "su" to another user. We are setting the path of the agent, so when the "su" happens it will already have the path. Just an FYI