GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: swlist - restoring data
Operating System - HP-UX
1845515
Members
2499
Online
110244
Solutions
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
Forums
Categories
This widget could not be displayed.
Company
This widget could not be displayed.
Local Language
This widget could not be displayed.
back
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
back
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
Blogs
Information
This widget could not be displayed.
This widget could not be displayed.
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- This widget could not be displayed.This widget could not be displayed.This widget could not be displayed.This widget could not be displayed.This widget could not be displayed.This widget could not be displayed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2007 05:00 AM
02-09-2007 05:00 AM
swlist - restoring data
We are on HP-UX 11.11.
We were experimented with the new Apache, so to be safe before we started we saved off /opt/hpws/apache to /opt/hpws/apache.old.
Then we installed the new Apache....which led us to installing a new PERL,etc.
For various reasons, we gave up and wanted to get back to our original configuration.
To make sure we could get back we moved /opt/hpws/apache to /opt/hpws/apache.new and then moved apache.old to apache. Apache came up fine and was the old version.
The issue is that doing it this way, when you do a "swlist" the version of Apache is incorrect (it shows the new version).
Is there a "good" way for us to not only get back to our older Apache, but have swlist, etc. also reflect we we are on the old version? (How can we get the new version of Apache out of the SW files and get the old one back in)?
Thanks!
We were experimented with the new Apache, so to be safe before we started we saved off /opt/hpws/apache to /opt/hpws/apache.old.
Then we installed the new Apache....which led us to installing a new PERL,etc.
For various reasons, we gave up and wanted to get back to our original configuration.
To make sure we could get back we moved /opt/hpws/apache to /opt/hpws/apache.new and then moved apache.old to apache. Apache came up fine and was the old version.
The issue is that doing it this way, when you do a "swlist" the version of Apache is incorrect (it shows the new version).
Is there a "good" way for us to not only get back to our older Apache, but have swlist, etc. also reflect we we are on the old version? (How can we get the new version of Apache out of the SW files and get the old one back in)?
Thanks!
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2007 07:20 AM
02-09-2007 07:20 AM
Re: swlist - restoring data
>Is there a "good" way for us to not only get back to our older Apache ...
The only way to do that is to reinstall the old apache.
Otherwise what you should have done when you moved the old apache aside, is to fiddle with the IPD and move those directories too. This is not supported and my comments oversimplify the process, if it is at all possible.
What you could have done is install the new apache in an alternate root. (swinstall ... @ /path) If you can run apache from there, you're done. Otherwise you could have moved apache to apache.old and added a symlink to your alternate root location.
Unfortunately, you needed to decide when you installed the new apache whether you would be going back.
The only way to do that is to reinstall the old apache.
Otherwise what you should have done when you moved the old apache aside, is to fiddle with the IPD and move those directories too. This is not supported and my comments oversimplify the process, if it is at all possible.
What you could have done is install the new apache in an alternate root. (swinstall ... @ /path) If you can run apache from there, you're done. Otherwise you could have moved apache to apache.old and added a symlink to your alternate root location.
Unfortunately, you needed to decide when you installed the new apache whether you would be going back.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2007 08:11 AM
02-19-2007 08:11 AM
Re: swlist - restoring data
thanks for the advice - hopefully we will do this correctly next time
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP