vmunix in HP-UX 11.23

[John Guster]

Server rebooted after kernel tunables change, it is noticed that vmunix is not changed. Is this expected?
Thank you.

[A. Clay Stephenson]

If all the tunables that you changed were dynamic then that is expected behavior

[hpuxrox]

What are the timestamps on the files in /stand ? Did any of them change? Have the files in changed in /stand/current?

[John Guster]

some tunables are dynamic like dbc_max_pct, but some are not like maxfiles,semmni.

Here is info on the timestamps:
-rwxr-xr-x 3 root sys 27327112 Mar 29 10:15 vmunix
drwxr-xr-x 5 root sys 1024 Mar 29 10:22 current
drwxr-xr-x 5 root sys 1024 Apr 19 15:15 backup
-rw------- 1 root root 12 Apr 19 16:36 rootconf
lrwxr-xr-x 1 root root 15 Apr 19 16:36 system -> nextboot/system
lrwxr-xr-x 1 root root 7 Apr 19 16:36 nextboot -> current
lrwxr-xr-x 1 root root 14 Apr 19 16:36 bootfs -> current/bootfs
-rw-r--r-- 1 root sys 4688 Apr 19 16:36 ioconfig
drwxr-xr-x 2 root sys 1024 Apr 19 16:37 krs


$ ls -lrt
total 53584
-rwxr-xr-x 3 root sys 27327112 Mar 29 10:15 vmunix
drwxr-xr-x 3 root sys 1024 Mar 29 10:22 bootfs
-rw-r--r-- 1 root sys 147 Mar 29 10:22 README
drwxr-xr-x 2 root sys 1024 Apr 19 16:36 mod
-rw-r--r-- 1 root sys 3528 Apr 19 16:37 system
drwxr-xr-x 2 root sys 1024 Apr 19 16:37 krs
Thanks for your input.

[John Guster]

what does vmunix cover in HP-UX 11.23?

[Anshumali]

not sure what you mean by covering...

[Dennis Handly]

>what does vmunix cover in HP-UX 11.23?

Are you asking which tunables aren't dynamic on 11.23?
You can look at the Release Notes:
http://docs.hp.com/en/5990-6737/index.html
File Systems Tunable Parameters:
http://docs.hp.com/en/5990-6737/ch04s06.html

[perumal_2]

Hi

If the parameter is dynamic it wouldn't demand a reboot. When a reboot happens it is obvious that kernel rebuilded and the the system booted with the new kernel.
To understand more can you let us know what parameter you had changed.

Rgds
Perumal

[John Guster]

I had to reboot to have tunables take effect. But the vmunix is still in old time stamp. This is why I ask here.

[Steven E. Protter]

Shalom

kctune -l

As noted before, if everything you changed was dynamic there is no reason to update vmunix so it was not updated.

There also should have been a prompt if you wanted to make it permanent.

Sam does have a view option that lets you see the underlying commands.

If however you changed a static parameter, then to get the kernel into production you would need to choose the "process kernel" option which would compile a new kernel and put it into production.

Its worth learning how to do this on the command line SAM fails to work or screws up at the most inconvenient times.

SEP

[Bill Hassell]

When you change a kernel parameter, whether it changes the size of the executable (vmunix) or not is a question of whether additional instructions or data elements are needed. For example, changing nproc from 1000 to 1000000 will have little effect on the vmunix file because the table is created in memory, not in the vmunix file. If you add or remove a driver, then the vmunix file will change size.