- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Best way to do tuning in /stand/vmunix after kerne...
Operating System - HP-UX
1754852
Members
5828
Online
108827
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
03-18-2010 05:25 AM
03-18-2010 05:25 AM
Best way to do tuning in /stand/vmunix after kernel rebuild?
Hi all,
I'm testing some of the new ONC/NFS patch NFS tuning parameters, such as async_read_avoidance_enabled.
The patch instructions say to use "adb" to insert the changes into the running kernel and the /stand/vmunix file, but warn that the change will be lost when the kernel is rebuilt.
What's the best way to insure that the change is inserted following the kernel build? I assume they can't simply be tacked on to /stand/system or the patch instructions would have mentioned that.
Is there any mechanism by which mk_kernel or the swinstall system can be made to apply the tuning tweaks following a rebuild but before the reboot, or should I just stick it into an rc1.d script?
Thanks for any suggestions.
I'm testing some of the new ONC/NFS patch NFS tuning parameters, such as async_read_avoidance_enabled.
The patch instructions say to use "adb" to insert the changes into the running kernel and the /stand/vmunix file, but warn that the change will be lost when the kernel is rebuilt.
What's the best way to insure that the change is inserted following the kernel build? I assume they can't simply be tacked on to /stand/system or the patch instructions would have mentioned that.
Is there any mechanism by which mk_kernel or the swinstall system can be made to apply the tuning tweaks following a rebuild but before the reboot, or should I just stick it into an rc1.d script?
Thanks for any suggestions.
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP