HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- about dynamic kernel parameter
Operating System - HP-UX
1834914
Members
2742
Online
110071
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
09-25-2002 05:31 PM
09-25-2002 05:31 PM
There are some dynamic kernel parameters on 11i.I know the machine have not to reboot if I change dynamic parameter,but when the machine reboot,why dynamic parameter is changed to the value before?
(l2000,11i)
(l2000,11i)
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2002 05:50 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2002 05:52 PM
09-25-2002 05:52 PM
Re: about dynamic kernel parameter
Dynamic tunables are not preserved after a reboot. DocId: UKRNKBRC00010259 Updated: 8/2/02 4:57:00 AM
PROBLEM
Using kmtune or Sam to set dynamic kernel parameters is losing the
value after a reboot.
For example:
# kmtune -s shmmax=0x40000000
# kmtune -u
The kernel's value of shmmax has been set to 1073741824 (0x40000000).
# kmtune -l -q shmmax
Parameter: shmmax
Current: 0x40000000
Planned: 0x40000000
Default: 0X4000000
Minimum: -
Module: -
Version: -
Dynamic: Yes
Everything appears to work, but when the system is rebooted with
shutdown -r, the values revert back to a previous setting.
What is going on?
RESOLUTION
In this case, the krsd daemon was not running so the configuration
files in /stand/krs/ were not getting updated. The krsd daemon should be
started in /etc/inittab as follows:
krsd:123456:respawn:/sbin/krsd -i
If this is not there, it should be added. Then do init q.
Once the daemon is restarted, the files in /stand/krs should be rebuilt. This
can be done with the kmtune command. In this example shmmax is being modified,
but using kmtune -s on any dynamic parameter would work:
# mv /stand/krs/* /tmp
# kmtune -s shmmax=0x40000000
# kmtune -u
Using cksum on the new files in /stand/krs will probably show
different sizes than the original ones. This is because the new values have
now been set correctly.
# cksum /stand/krs/*
4067031556 65048 /stand/krs/_stand_vmunix.krs
3908630881 24 /stand/krs/system.krs
The kernel parameter value should now survive a reboot.
PROBLEM
Using kmtune or Sam to set dynamic kernel parameters is losing the
value after a reboot.
For example:
# kmtune -s shmmax=0x40000000
# kmtune -u
The kernel's value of shmmax has been set to 1073741824 (0x40000000).
# kmtune -l -q shmmax
Parameter: shmmax
Current: 0x40000000
Planned: 0x40000000
Default: 0X4000000
Minimum: -
Module: -
Version: -
Dynamic: Yes
Everything appears to work, but when the system is rebooted with
shutdown -r, the values revert back to a previous setting.
What is going on?
RESOLUTION
In this case, the krsd daemon was not running so the configuration
files in /stand/krs/ were not getting updated. The krsd daemon should be
started in /etc/inittab as follows:
krsd:123456:respawn:/sbin/krsd -i
If this is not there, it should be added. Then do init q.
Once the daemon is restarted, the files in /stand/krs should be rebuilt. This
can be done with the kmtune command. In this example shmmax is being modified,
but using kmtune -s on any dynamic parameter would work:
# mv /stand/krs/* /tmp
# kmtune -s shmmax=0x40000000
# kmtune -u
Using cksum on the new files in /stand/krs will probably show
different sizes than the original ones. This is because the new values have
now been set correctly.
# cksum /stand/krs/*
4067031556 65048 /stand/krs/_stand_vmunix.krs
3908630881 24 /stand/krs/system.krs
The kernel parameter value should now survive a reboot.
Did you take a backup?
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