- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: shmmax value
Operating System - HP-UX
1753796
Members
6709
Online
108799
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
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
03-07-2009 08:41 AM
03-07-2009 08:41 AM
Re: shmmax value
while i am giving this
root@lust:>kmupdate
kmupdate: Newly built kernel /stand/build/vmunix_test is not found.
I am getting error as above. Please suggest what may be the issue
root@lust:>kmupdate
kmupdate: Newly built kernel /stand/build/vmunix_test is not found.
I am getting error as above. Please suggest what may be the issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2009 10:19 AM
03-07-2009 10:19 AM
Re: shmmax value
Hi Amit,
1.) Procedure to generate a kernel at UX 11.00
1) Change to the kernel generation working directory and remove the files that have been left over from the last kernel generation:
# cd /stand/build
# rm -r * (Be careful with this! You need to be in /stand/build/)
2) Backup the current system file:
# cp /stand/system /stand/system.prev
7/33 Kernel Configuration Jan 2004
3) Is the system file up to date?
If you are not sure that the current system file (/stand/system) corresponds to the current kernel (/stand/vmunix), then use the system_prep script to extract a system file from the current kernel:
# /usr/lbin/sysadm/system_prep [-s /stand/system]
Compare the new system file to the original one. The diff command should not produce any results:
# diff /stand/system /stand/system.prev
4) Modify the system file
Use kmtune(1M) to modify kernel tunables. Use kmsystem(1M) to add/remove driver. These commands do nothing more than modifying /stand/system. Due to various dependencies, the system file should not be edited by hand. E.g.:
# kmtune -s shmmax= (changes tunable in system files)
5) Generate the kernel
After you modified the system file, you can generate the new kernel using the mk_kernel script. The name of the new kernel will be /stand/build/vmunix_test, unless explicitly specified through the -o option. The -s option specifies the system file to use, /stand/system is the default:
# mk_kernel
6) Schedule kernel update
kmupdate is used to initiate the move of the new kernel (/stand/build/vmunix_test) and the corresponding files to their appropriate places at the next shutdown or startup. The current kernel will be copied to /stand/vmunix.prev, then.
# kmupdate
7) Restart the system
The new kernel will be activated by restarting the system:
# cd /
# shutdown -ry now
1.) Procedure to generate a kernel at UX 11.00
1) Change to the kernel generation working directory and remove the files that have been left over from the last kernel generation:
# cd /stand/build
# rm -r * (Be careful with this! You need to be in /stand/build/)
2) Backup the current system file:
# cp /stand/system /stand/system.prev
7/33 Kernel Configuration Jan 2004
3) Is the system file up to date?
If you are not sure that the current system file (/stand/system) corresponds to the current kernel (/stand/vmunix), then use the system_prep script to extract a system file from the current kernel:
# /usr/lbin/sysadm/system_prep [-s /stand/system]
Compare the new system file to the original one. The diff command should not produce any results:
# diff /stand/system /stand/system.prev
4) Modify the system file
Use kmtune(1M) to modify kernel tunables. Use kmsystem(1M) to add/remove driver. These commands do nothing more than modifying /stand/system. Due to various dependencies, the system file should not be edited by hand. E.g.:
# kmtune -s shmmax=
5) Generate the kernel
After you modified the system file, you can generate the new kernel using the mk_kernel script. The name of the new kernel will be /stand/build/vmunix_test, unless explicitly specified through the -o option. The -s option specifies the system file to use, /stand/system is the default:
# mk_kernel
6) Schedule kernel update
kmupdate is used to initiate the move of the new kernel (/stand/build/vmunix_test) and the corresponding files to their appropriate places at the next shutdown or startup. The current kernel will be copied to /stand/vmunix.prev, then.
# kmupdate
7) Restart the system
The new kernel will be activated by restarting the system:
# cd /
# shutdown -ry now
"Light travels faster than sound. That's why some people appear bright until you hear them speak."
- « Previous
- Next »
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