Sponsored Content
Full Discussion: So_keepalive
Operating Systems AIX So_keepalive Post 302207090 by bakunin on Thursday 19th of June 2008 06:06:41 AM
Old 06-19-2008
zaxxon is right, tcp_keepinit is probably the culprit here.

All these values can be set with the "no" command (see "man no" on how to do it along with a explanation of what the items do). All these changes made through "no" will be volatile, not surviving the next reboot.

If you want to make them lasting change the file /etc/tunables/nextboot accordingly.

I hope this helps.

bakunin
 
semvmx(5)							File Formats Manual							 semvmx(5)

NAME
semvmx - maximum value of any single System V IPC semaphore VALUES
Failsafe Default Allowed values DESCRIPTION
The tunable specifies the maximum value any given System V IPC semaphore can have. If an application attempt to exceed this limit, it will receive an error from or from For more information about System V semaphores, refer to the section of the sema(5) manpage. Who Is Expected to Change This Tunable? Anyone. Restrictions on Changing Changes to this tunable take effect at the next reboot. Note: If the DynSysVSem optional product bundle is installed increases in the tunable value take effect immediately; decreases in the tun- able value take effect at the next reboot. When Should the Value of This Tunable Be Raised? If an application requires larger semaphore values. When Should the Value of This Tunable Be Lowered? If requirements for the single semaphore value has decreased, or if there for limit protection on run-away applications which change sema- phores. What Other Tunable Values Should Be Changed at the Same Time? All the System V semaphore tunables are interrelated and should not be treated as independent variables. The tunables must be evaluated as a system to ensure they reflect the application requirements. The semaphore tunables include and Consider changes to when changing Note: If the DynSysVSem optional product bundle is installed then the and tunables are ignored and have no effect. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by AT&T. SEE ALSO
semop(2), semctl(2), sema(5), semaem(5), semmni(5), semmns(5), semmnu(5), semmsl(5), semume(5), sysv_hash_locks(5). Tunable Kernel Parameters semvmx(5)
All times are GMT -4. The time now is 07:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy