- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- permanent bourne shell environment change
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2009 06:11 PM
тАО02-10-2009 06:11 PM
export DP_JAVA_DIR=/opt/java1.5/jre/
And this works: I see it when I type:
env
And DP6.1 starts up without displaying the "your JRE version is wrong" message that I was getting *before* performing the export.
But, after I shut down the DP6.1 GUI and the data space where I performed the export, the environment reverts back to the state it was in before I performed the export. In other words, it loses the pointer to java.
How do I get the java pointer in the environment so that it stays there even after I shut down the data space?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2009 06:33 PM
тАО02-10-2009 06:33 PM
Re: permanent bourne shell environment change
You can put that export in your .profile.
Is there some configuration file for DP where you can add it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2009 07:01 PM
тАО02-10-2009 07:01 PM
Re: permanent bourne shell environment change
just add that line to the .profile of login that is running xomni. Or, if that would cause problems with other programs - just write a script file that runs xomni for you, and in THAT script add the export.
----------suggested script below---------
#!/bin/ksh
export DP_JAVA_DIR=/opt/java1.5/jre/
/opt/omni/bin/xomni
------------------------------------
Now save that script as DP6,
and do a "chmod u+x" on the file to make it executable. Then put it in the path for your user, or add a directory to your path and put it in there, like /home/TMug/bin
and put your script in there. So, anytime you type "DP6" it will kick off your export and then run your omniback (ne' data protector) interface.
Hope that helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2009 07:24 PM
тАО02-13-2009 07:24 PM
Re: permanent bourne shell environment change
TwoProc - You said "Then put it in the path for your user, or add a directory to your path". I assume you refer to the path as shown in the environment. This is the problem => I don't know how to do that. I think maybe that is what I should really be asking. How do I add the new path to the "PATH=" in the environment?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2009 07:54 PM
тАО02-13-2009 07:54 PM
Solution> did not solve the problem [...]
You also need to have the shell (re-)read
your "~/.profile" file, so log in again, or:
. ~/.profile
(Unless you're using a C shell, which doesn't
look at "~/.profile".)
Note that we can't see what's in your
"~/.profile", and we can't see exactly what
you're doing after you change it, all of
which makes it hard to say why things aren't
working as expected.
> How do I add the new path to the "PATH="
> in the environment?
Depending on exactly what you want:
PATH="new_dir:${PATH}"
or
PATH="${PATH}:new_dir"
Again, adding this to your "~/.profile" may
be useful, depending on what's in there
already.
ls -l ~/.profile
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2009 08:52 PM
тАО02-13-2009 08:52 PM
Re: permanent bourne shell environment change
I vi'd into it and added the path, then logged out and logged back in, and viola`. Also, just to play around and maybe learn something, I un-did my change to the .PATH file, logged out, back in, and issued the command:
PATH=$PATH:{path}
then logged out and back in, and same thing, only a lot easier, only I'm not certain that I actually needed to log out and back in at that point. At any rate, problem solved. Thanks to all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-15-2009 01:26 AM
тАО02-15-2009 01:26 AM
Re: permanent bourne shell environment change
This must be specific to your system.
>I'm not certain that I actually needed to log out and back in
You can always source your .profile or execute the command in question.