MAXUSERS change without using SAM

[hpuxhelp]

how can I change the maxuser paramter without using SAM?

is this require a reboot?? since it creates a change in the kernel

[Bill Hassell]

MAXUSERS is not a kernel parameter at all. It is a formula macro that affects about 4-5 different parameters. NOTE: MAXUSERS has NOTHING to do with the number of user that can log onto the system. SAM is the tool that makes the calculations which are then translated into a numeric value. All of the parameters that use MAXUSERS will require a reboot once they are changed.

[KCS_1 · Accepted solution]

Hi,

why you change the parameter without using SAM?? I think this way is the best to change that.

However, you can change that by command on prompt.

Look at 'kmtune' manpage

(hp-ux 11i)
#kmtune -l |more


Parameter: maxusers
Current: 32
Planned: 32
Default: 32
Minimum: -
Module: -
Version: -
Dynamic: No <---- rebooting required



# kmtune -s maxusers = new_value




# kmtune -l | grep -i maxusers
Parameter: maxusers
Planned: (100+16*MAXUSERS)
Default: (100+16*MAXUSERS)
Planned: (16*(NPROC+16+MAXUSERS)/10+32+2*(NPTY+NSTRPTY+NSTRTEL))
Default: (16*(NPROC+16+MAXUSERS)/10+32+2*(NPTY+NSTRPTY+NSTRTEL))
Planned: ((NPROC+16+MAXUSERS)+32+(2*NPTY))
Default: ((NPROC+16+MAXUSERS)+32+(2*NPTY))
Planned: (20+8*MAXUSERS)
Default: (20+8*MAXUSERS)


As you see above output, some of kernel parameters related. that's why you need reboot system for making new kernel as well.






Have a good day!

-Best Regards

Patrick

[Steven E. Protter]

kmtune -s maxuser=128

# cd /stand/build
# /usr/lbin/sysadm/system_prep -s system
# vi system (make your changes)
save file
# /usr/sbin/mk_kernel -s system
# /usr/sbin/kmupdate

SEP

[hpuxhelp]

after changing the paramter , I did the reboot...once this is up, the new kernel will take into affect??

[KCS_1]

Yup! Absolutly!

after building a new kernel to moved new one and will be rebooted with taking effection.

In my case, I always remain two copy files that /stand/system and /stand/vmunix such as stand.copy, vmunix.copy

[Steven E. Protter]

If you copied the new kernel to /stand/vmunix the and booted, the machine now reflects the changed value.

kmtune to check it.

SEP

[hpuxhelp]

when I did kmtune -d
i saw this
Parameter Current Dyn Planned Module Version
===============================================================================
maxusers 32 - 128
msgmnb 16384 Y 65536

does this mean the new changes didn't take place?? why it said the current is still at 32 instead of 128???

[KCS_1]

Ah! you didn't get the next procedure to building for new kernel. right??


------------------------------------------
#kmtune -s maxuser=128
# cd /stand/build
# /usr/lbin/sysadm/system_prep -s system
# /usr/sbin/mk_kernel -s system
# /usr/sbin/kmupdate
--------------------------------------------
above Steven has posted next procedure how to make this.

[KCS_1]

Afer then , go to the Reboot!!

# kmtune -q maxusers

128-128 (affected the value)