10-08-2010
These are the 3 relevant tunables:
Quote:
tcp_keepalive_time
The interval between the last data packet sent (simple ACKs are not considered data) and the first keepalive probe; after the connection is marked to need keepalive, this counter is not used any further.
tcp_keepalive_intvl
The interval between subsequential keepalive probes, regardless of what the connection has exchanged in the meantime.
tcp_keepalive_probes
The number of unacknowledged probes to send before considering the connection dead and notifying the application layer.
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
LEARN ABOUT DEBIAN
smokeping_probes_sipsak
Smokeping_probes_SipSak(3) SmokePing Smokeping_probes_SipSak(3)
NAME
Smokeping::probes::SipSak - tests sip server
OVERVIEW
This probe sends OPTIONS messages to a sip server testing the latency.
SYNOPSIS
*** Probes ***
+SipSak
binary = /usr/bin/sipsak
forks = 5
offset = 50%
step = 300
timeout = 15
# The following variables can be overridden in each target section
keep_second = yes
params = --numeric --password=mysecret
pings = 5
port = 5061
user = nobody
# [...]
*** Targets ***
probe = SipSak # if this should be the default probe
# [...]
+ mytarget
# probe = SipSak # if the default probe is something else
host = my.host
keep_second = yes
params = --numeric --password=mysecret
pings = 5
port = 5061
user = nobody
DESCRIPTION
The probe uses the sipsak <http://sipsak.org/> tool to measure sip server latency by sending an OPTIONS message.
The sipsak command supports a large number of additional parameters to fine-tune its operation. Use the params variable to configure them.
VARIABLES
Supported probe-specific variables:
binary
The location of your echoping binary.
Default value: /usr/bin/sipsak
forks
Run this many concurrent processes at maximum
Example value: 5
Default value: 5
offset
If you run many probes concurrently you may want to prevent them from hitting your network all at the same time. Using the probe-
specific offset parameter you can change the point in time when each probe will be run. Offset is specified in % of total interval, or
alternatively as 'random', and the offset from the 'General' section is used if nothing is specified here. Note that this does NOT
influence the rrds itself, it is just a matter of when data acqusition is initiated. (This variable is only applicable if the variable
'concurrentprobes' is set in the 'General' section.)
Example value: 50%
step
Duration of the base interval that this probe should use, if different from the one specified in the 'Database' section. Note that the
step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you'll have to
delete the old RRD files or somehow convert them. (This variable is only applicable if the variable 'concurrentprobes' is set in the
'General' section.)
Example value: 300
timeout
How long a single 'ping' takes at maximum
Example value: 15
Default value: 5
Supported target-specific variables:
keep_second
If OPTIONS is actually implemented by the server, SipSak will receive two responses. If this option is set, the timeing from the
second, final response will be counter
Example value: yes
params
additional sipsak options. The options will get split on space.
Example value: --numeric --password=mysecret
pings
How many pings should be sent to each target, if different from the global value specified in the Database section. Note that the
number of pings in the RRD files is fixed when they are originally generated, and if you change this parameter afterwards, you'll have
to delete the old RRD files or somehow convert them.
Example value: 5
port
usa non-default port for the sip connection.
Example value: 5061
user
User to use for sip connection.
Example value: nobody
AUTHORS
Tobias Oetiker <tobi@oetiker.ch> sponsored by ANI Networks
2.6.8 2013-03-17 Smokeping_probes_SipSak(3)