HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- moving from legacy package to modular package sg 1...
Operating System - HP-UX
1834018
Members
2180
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2007 01:49 AM
12-19-2007 01:49 AM
Hi All,
I need to move my packages from legacy to modular.
I have several questions:
1. is a control script for RUN and HALT generated for each package?
2. IN my Legacy packages, I had some operations that I needed to do just as the volume groups are starting, and right before they are going offline,
How can I achieve that on the mofdular packager? the external_scripts, and pre scripts, are not called on the correct time for my needs.
Thanks,
Anat
I need to move my packages from legacy to modular.
I have several questions:
1. is a control script for RUN and HALT generated for each package?
2. IN my Legacy packages, I had some operations that I needed to do just as the volume groups are starting, and right before they are going offline,
How can I achieve that on the mofdular packager? the external_scripts, and pre scripts, are not called on the correct time for my needs.
Thanks,
Anat
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2007 03:11 AM
12-20-2007 03:11 AM
Solution
1. There is no control script generated for each package. There is a framework which calls various scripts and does things dependent on the package configuration options. You can see the scripts which are used in $SGCONF/scripts.
2. If you modified code outside of the customer_defined_run/halt_cmds functions in your legacy packages then you were doing things which were unsupported and it is highly likely that you will not be able to do this with modular packages.
The expectation is that with modular packages you use the hooks provided i.e. those defined by external_script and external_pre_script. If you need things to be run at times other than when these are run you have a problem.
You could potentially create your own modules and scripts and modify the master scripts but again you would be completely unsupported doing this.
2. If you modified code outside of the customer_defined_run/halt_cmds functions in your legacy packages then you were doing things which were unsupported and it is highly likely that you will not be able to do this with modular packages.
The expectation is that with modular packages you use the hooks provided i.e. those defined by external_script and external_pre_script. If you need things to be run at times other than when these are run you have a problem.
You could potentially create your own modules and scripts and modify the master scripts but again you would be completely unsupported doing this.
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 2025 Hewlett Packard Enterprise Development LP