1831210 Members
3038 Online
110021 Solutions
New Discussion

System-imposed value

 
Gerardo Mora
Advisor

System-imposed value

OS : HP-UX 10.20
Hardware: HP-9000 T-600

I would like to know what is the system-imposed value and how can I changed it, because has a too low value for shared memory segment size.

Thank You!
Gerardo Mora
share to learn
4 REPLIES 4
James R. Ferguson
Acclaimed Contributor

Re: System-imposed value

Hi:

Use SAM and to Configure Kernal Parameters. SAM has some good builtin help on the affect and range of each kernel parameter. Change your parameters with SAM. It enforces inter-parameter relationships and enables you to generate a well-tuned kernel. For additional information on kernel parameters see:

http://www.docs.hp.com/hpux/content/KCparams.OverviewAll.html

...JRF...
CHRIS_ANORUO
Honored Contributor

Re: System-imposed value

Changing shared memory values through SAM under kernel configuration will as always require a sytem reboot. See the document link and also the attached documentation.
http://www.docs.hp.com/hpux/content/KCparam.ShMemParmsOverview.html
When We Seek To Discover The Best In Others, We Somehow Bring Out The Best In Ourselves.
Rick Garland
Honored Contributor

Re: System-imposed value

Using SAM to change kernel values is a better way to go. Some of the kermel values have defined ranges that SAM is aware of as opposed to modification of the /stand/build/system file. When using the system file, you are not prompted to values that may be out of range and as a result you could build a kernel that is un-bootable. SAM will tell you what the defined ranges are. There are good articles regarding kernel values and their impact on system performance. It would be a good idea to read up on the kernel values before changing. Remember, change one value and it could very well have an affect on another value. This could be an adverse affect.
Rick Garland
Honored Contributor

Re: System-imposed value

Using SAM to change kernel values is a better way to go. Some of the kermel values have defined ranges that SAM is aware of as opposed to modification of the /stand/build/system file. When using the system file, you are not prompted to values that may be out of range and as a result you could build a kernel that is un-bootable. SAM will tell you what the defined ranges are. There are good articles regarding kernel values and their impact on system performance. It would be a good idea to read up on the kernel values before changing. Remember, change one value and it could very well have an affect on another value. This could be an adverse affect.