Kernel Parm Changes

[Tonya Underwood]

I rebooted this server yesterday to put into place vps_ceiling at 64 and maxssiz_64bit at 1073741824.

It appears these kernel parameters are now at those values. However when I do a kmtune to query the values, it states a PLANNED value of what the value was before... why?

Thanks,
Tonya Underwood


# kmtune -q vps_ceiling
Parameter Current Dyn Planned Module Version
===============================================================================
vps_ceiling 64 - 16
# kmtune -q maxssiz_64bit
Parameter Current Dyn Planned Module Version
===============================================================================
maxssiz_64bit 1073741824 - 960000000
#

[Steven E. Protter · Accepted solution]

Shalom,

Probably you did not move the system file to its permanent location.

Did you use SAM or do it manually. If you did it manually you need to post your procedure and then someone will tell you where the mistake happened.

SEP

[Tonya Underwood]

cd /stand/build
cp /stand/build/system system
/usr/lbin/sysadm/system_prep -s system
made changes in my system file
mk_kernel -s system
cp /stand/system /stand/system.prev
cp /stand/vmunix /stand/vmunix.prev
cp -R /stand/dlkm /stand/dlkm.prev
kmupdate

[Tonya Underwood]

Oops... I meant

cp /stand/system /stand/build/system

[A. Clay Stephenson]

maxssiz_64bit at 1073741824

This is a ludicrous value for stacksize whether it is 32-bit or 64-bit code. Only extremely badly written code would ever need a stack larger than 64MiB (and that is extremely generous). If a vendor is requesting a stack that large then find a baseball bat. You will need it to adjust the top of his skull downward.

[Tonya Underwood]

Well... I forgot to move my system file (new one)... just looked at my steps and realized. Thanks Steven! DUH!

And yes it's a ludicrous value.