10-08-2010
Those tunables are only active/applicable if the app uses SO_KEEPALIVE() in the program, correct? unfortunately, our original developers didnt seem to think it was a necessary evil.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi! Experts,
Could someone tell me how to set a time out for xterm users.. I have set TMOUT which logs out telnet users after sometime..
The users here use exceed to connect to Xterm server. So, it doesnt kill xterm windows that have not been used even for 7 days..
Is there any work... (1 Reply)
Discussion started by: jyotipg
1 Replies
2. Solaris
Hello;
I have Solaris 2.6 installed on many Sun AXI Ultra Sparc IIi systems. I want to set the Lock Screen global timeout for all users to 15 minutes. I read the Solaris CDE guide which instructed me to create a /etc/dt/config/C/sys.resources file and changed the timout to 15 minutes in... (1 Reply)
Discussion started by: rambo15
1 Replies
3. AIX
Hi all
Can any one solve my problem? I want to change the default timeout setting for telnet in aix, pls help me. (1 Reply)
Discussion started by: vjm
1 Replies
4. UNIX for Advanced & Expert Users
Hi,
I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime.
To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies
5. Shell Programming and Scripting
Hi
I am using mpssh client for parallel ssh connections. I need help in setting the timeout for the parallel sessions say 30 seconds. Plz Help.
Thanks in advance
M.S.Srivatsa
Double post, continued here (0 Replies)
Discussion started by: mssrivatsa
0 Replies
6. UNIX for Advanced & Expert Users
Hi
I am using mpssh client for parallel ssh connections. I need help in setting the timeout for the parallel sessions say 30 seconds overall. Plz Help.
Thanks in advance
M.S.Srivatsa (0 Replies)
Discussion started by: mssrivatsa
0 Replies
7. IP Networking
I need clarification on whether it is okay to set socket options on a listening socket
simultaneously when it is being used in an accept() call?
Following is the scenario:-
-- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Discussion started by: jake24
2 Replies
8. Solaris
Hi All
I need to set timeout of login session of a user if a user is idle for some time.
I know the TMOUT setting but it work with only BASH & KORN shell only as I need to set for Bourne shell also. I am trying to put "ClientAliveInterval 300" in sshd_config & restart or refreshing the... (1 Reply)
Discussion started by: sb200
1 Replies
9. IP Networking
Hello,
I detect these errors in my logs :
Socket timeout calling url http://server:port/bla/soap/selfcare/infoRapide]
Unable to make proxyRequest
I've made a tcpdump capture this way :
tcpdump -i eth0 -s 0 -w /app/captura.pcap port 8080
But I'm fairly new in reading .pcap files with... (0 Replies)
Discussion started by: black_fender
0 Replies
10. Shell Programming and Scripting
Hi
I'm writing a script which based on a condition, restarts a set of servers. The problem I'm facing is, say if one of the server is down, my script stops there and fails to proceed. How can I ensure to set a timeout value on that script, so when the server is not reachable, the script should... (2 Replies)
Discussion started by: mathbalaji
2 Replies
semmns(5) File Formats Manual semmns(5)
NAME
semmns - number of System V IPC system-wide semaphores
VALUES
Failsafe
Default
Allowed values
DESCRIPTION
The tunable specifies the maximum total individual System V IPC system-wide semaphores which can be assigned by applications. Semaphores
are assigned in "sets" associated with an ID. Thus semaphores can be distributed in any manner across the range of IDs with one or more
per ID.
There is no reason to specify less than (the maximum number of identifiers) as each ID requires at least one semaphore.
If an application attempts to create a semaphore set with more semaphores than are remaining, it will receive an error 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 then changes to this tunable take effect immediately.
When Should the Value of This Tunable Be Raised?
If applications require more total semaphores in the system.
When Should the Value of This Tunable Be Lowered?
If requirements for semaphores has decreased, or there is a need to hard-limit applications from acquiring larger numbers of semaphores.
What Are the Side Effects of Lowering the Value?
The following side effect applies only if the DynSysVSem optional product bundle is installed.
If DynSysVSem is installed, lowering the value of this tunable increases the risk of application failure due to the inability to create
more semaphore sets. Lowering the tunable has no effect on any active semaphores in their respective sets, even if the new tunable value
is less than the number of semaphores already created on the system. However, no new semaphore sets may be created until the number of
active semaphores on the system falls below the setting of
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 Typically, a change in the tunable does
not require changes to other tunables.
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
semget(2), sema(5), semaem(5), semmni(5), semmnu(5), semmsl(5), semume(5), semvmx(5), sysv_hash_locks(5).
Tunable Kernel Parameters semmns(5)