10.2 equivalent of kmtune?

[Jeff Schussele]

All,

It's been so long since I've had to script for 10.2 & I could use some help. I have a checkinstall script for a package I need to modify to install on 10.2 system that uses kmtune commands to get specific kernel parameters & 10.2 does not have that command.
Did 10.2 have an equivalent command that anybody remembers?

I know I can grep the system file, but as you know that's not a guarantee of the actual value. I've run up SAM & checked the samlog, but it just lists functions such as KC_GET_PARAMS & kc_get_sys_info. Anybody know where these functions live?

Any help would be greatly appreciated.

Thanks,
Jeff

[Pete Randall]

Jeff,

The word "sysdef" is banging around in my empty head. I don't know if that's it or not but I needed to get it out!!

;^)


Pete

[Helen French]

This command might help:

# sysdef

[Steven E. Protter]

Jeff, I have 10.x manuals in my office.

They appear to agree with the sysdef statement.

Just confirmation, points not necessary.

Congrats to you on a nice week last week(stats).

SEP

[Jeff Schussele]

Thanks guys, but it appears sysdef only gives me values that have been changed since install. But come to think of it, maybe if it's NOT in sysdef output, that might make the system file "reliable".
What do you think?

Anything else?

Rgds,
Jeff

[Steven E. Protter]

I don't think you can change kernel values with sysdef, just display them.

But you've figured that out.

Back when I did 10.20, I used sam for kernel changes. I don't have much stick time on 10.20 though.

SEP

[Helen French]

'sysdef' will check the currently running system (kernel) and will report its *tunable* configuration parameters. It should display all tunable parameters even if you haven't changed it since install.

/stand/system file also is useful in your case. I would check if you can find the command executed by SAM when it retrieves the tunable parameters.

[Pete Randall]

Jeff,

That's not the way the man page reads (at least not on 11i, anyway). Sysdef should report on all the configurable parameters.


Pete

[Jeff Schussele]

I might have that backwards - i.e. sysdef gives defaults maybe.
By that I mean in this case I'm looking for the msgmax (and other msg??? parms)& I find them in the system file, but they're not in the sysdef output.
It seems sysdef won't let me query individual parms.

But I've checked *actual* settings & they match the system file's values. So I'm thinking I'll just use the system file as this is only going to go on a few systems that won't be 10.2 for very long.....If we get our way.

Jeff

[Helen French]

I see what you are saying. Check and see if these commands would be helpful:

# cat /usr/conf/master.d/core-hpux | grep max*

# /usr/lbin/sysadm/system_prep -s /tmp/system

# /usr/lbin/sysadm/get_sysfile /stand/vmunix | pg

[Jeff Schussele]

Guys,

Here's what I'm seeing. Attached is a concatenated file - kern_parms.txt. First part is sysdef output & the latter is the system file. I've added a divider to signify the split.

As you can see the values I want - msgmax/msgmnb/msgmni/msgtql - are in the system file but not in the sysdef output.

Jeff

[Pete Randall]

Jeff,

Interesting results! This is not what I'm seeing on my 11i system. Checking parameters that have obviously been changed (according to /stand/system) against sysdef output, I'm coming up with exactly the same output. For example, maxswapchunks is set to 1024 in /stand/system and "sysdef |grep maxswap" results in 1024 as well.

I wonder if there are any old 10.20 sysdef patches around???


Pete

[DIPAK KUMAR ROY]

"sysdef" command gives you actual current value of the kernel parameter ( may be different from /stand/system , in case somebody just edited /stand/system and didn't rebuild the kernel).

"kmtune" command takes the kernel parameter value from /stand/system. For example if you change kernel parameter "shmmax" to 12000000 on /stand/system and don't rebuild the kernel, kmtune will report it as 12000000, which is not correct.
BTW "kmtune" will fail if you rename /stand/system.

So "sysdef" and "kmtune" are not exactly same.

Thanks

[Bernhard Mueller]

Jeff,

I maybe wrong, but I believe that from SAM you could print *all* the values into a file, which would give you values that
/usr/lbin/sysadm/system_prep -k -s

would not list since they remained at default.

Regards,
Bernhard

[Helen French]

From what I am reading now, it looks like 'sysdef' command is not as reliable as SAM or /stand/system file. Like you said, it might be reporting parameters which were changed from *default*. I would go with system file if possible.

[Jeff Schussele]

Thanks all.
It appears that to be 100% sure I'd have to check both sysdef output & the system file.
I may just remove the check as the /usr/conf/master.d/core-hpux file shows that the values I'm concerned about do meet the minimum (barely) at their default settings.
I'll probably be betting (hoping) no SA out there lowered the dang things.
And as stated we only have a few systems (well few for us - dozens actually & NONE in our group anyway) that will install this package enterprise-wide & it'll just be up to the SA to bump the parm if they have trouble.

But it's been a great illustration as to why one should be at 11.0 or even better 11i.
I won't even go into the differences that layout_version 0.8 has over 1.0 & the silly changes required to accomodate that....

Bernhard - that would be nice & useful but this has to run during a non-interactive swinstall session & all I do in this script is stop the install & alert the SA via the log that the parm must be raised to a certain minimum value.

Points on the way.

Thanks again all,
Jeff