- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Package Startup
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
Forums
Discussions
Discussions
Discussions
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
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
05-28-2002 06:10 PM
05-28-2002 06:10 PM
Routinely, we have brought the package down, rebooted then brought the package up.
I am unsure of the AUTO_RUN parameter. If I set it to yes, will the package tried to failover if I reboot? This is not what I desire for a simple reboot to apply new kernel parms.
Thanks for any input.
dl
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 10:57 PM
05-28-2002 10:57 PM
SolutionThe simple alternative is to either do cmmodpkg -d pkg_name, so it will not switch at all, or do cmmodpkg -d pkg_name -n alternate_node_name to tell it it cannot switch to the alternate node.
For safety, I always suggest the package is halted prior to doing work like this to ensure it halted cleanly, thus ensuring that it should restart in a stable state.
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 11:22 PM
05-28-2002 11:22 PM
Re: Package Startup
I normally halt the package before doing any kernel params reboots. But as said before you can disable the package from switching.
Hilary
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 11:36 PM
05-28-2002 11:36 PM
Re: Package Startup
Regards,
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 11:41 PM
05-28-2002 11:41 PM
Re: Package Startup
I usually use a cmhaltpkg before to stop the node unless I need that the pakage still runing in other node, then I stop the pakage in the node and force to run in other node with the "cmrunpkg -n nodename pakagename" command.
It's better to stop the pakage cleanly before to stop the node, I think.
Hope this helps,
Justo.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2002 11:50 PM
05-28-2002 11:50 PM
Re: Package Startup
But I have seen packages failing to halt and switching when the system goes down so I do agree with Melwyn it's good practice to halt the packages before doing maintenance on the node.
Regards,
Trond
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2002 08:04 AM
05-29-2002 08:04 AM
Re: Package Startup
I believe I need to go with a combination of Melvyn's and John's answers.
Note that I did state we do halt the package prior to any reboot.
I just want the package to start up on reboot.
With this in mind, I will also build the shutdown script.
With the failure of clean shutdown noted, I will probably shut down manually prior to reboot.
I have not had the occasion to have to perform a reboot without being present or online.
Thanks for all the input.
dl