12-05-2003
Time Wait interval
What is the time_wait interval for Solaris 8/9??? and is it configurable???
For example sometimes a clients pc will freeze up dropping the connection, closing the port. The problem is on our side our system still thinks their logged in (until it realizes it dropped on the otherside and drops on our side) and won't let them in until about 6-10 minutes later.
Is there a way to configure the time_wait interval to something shorter.
any info you can spare will be much appreciated
Thanks in advance
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Ok, heres the situation. We use Solaris 8 and sometimes users who are logged into our system restart their pc's without shutting down the application that attached to our unix backend. I netstat and I get time-waits for the users.
My question is how long before the time-wait ends and the user... (1 Reply)
Discussion started by: eloquent99
1 Replies
2. Programming
Hi friends, I need to find average load on my server. The problem would have been quite simple had I required the load averaged over 1 min,5 min or 15 min which I can easily find reading /proc/loadavg (the same as shown by 'uptime') but my requirement compels me to find load averaged over 10 sec or... (2 Replies)
Discussion started by: Rakesh Ranjan
2 Replies
3. Shell Programming and Scripting
Hi Guys,
I have two dates as start date and end date.. i need to generate files within these two dates with time interval of half an hour....
i.e. Start Date=25/09/07 12:00:00
End Date=26/09/07 12:00:00
Now i need to generate files every half an... (0 Replies)
Discussion started by: aajan
0 Replies
4. Shell Programming and Scripting
I want a shell script which extract data from a log file which contains date and time-wise data and i need the data for a perticular interval of time...what can i do??? (3 Replies)
Discussion started by: abhishek27
3 Replies
5. Shell Programming and Scripting
Hi ,
I am working on the following script . I want this script to run and scan the log file repeatedly after 3 hours. This script will run & scan just for the current date logs and after every 3 hours. Kindly advice what to add in this script for this purpose.
#!/bin/sh
diff common.log... (3 Replies)
Discussion started by: himvat
3 Replies
6. UNIX for Dummies Questions & Answers
I have a script I want to run in the background, and I have looked it up but I am not exactly sure how to do. First of all to run it in the background do you have to put something in the script or is it just a command when you go to run it. I found this solution to it but once again I am not to... (2 Replies)
Discussion started by: mauler123
2 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
I am new to this forum....
Can neone please help me how to copy files between two time intervals i.e. I need to copy files from 6.30 to 9.30 on 5th June 09.
Any help is appreciated. (2 Replies)
Discussion started by: Pratik4891
2 Replies
8. Shell Programming and Scripting
Hi,
Can someone help me in running a cronjob everyday between 7 and 8 pm with the time interval of 5 minutes in between to repeat that script. The script is so small and I need that to run daily between this time. Please if possible provide me the syntax for this logic.
Thanks. (4 Replies)
Discussion started by: cya
4 Replies
9. Shell Programming and Scripting
Folks,
I need to send a .log file to my email for every one hour from a server that too only in a particular time period. Is awk mandate here? or can we do it in shell scripting only? Please help me in sorting this out.
Cheers,
Arun (3 Replies)
Discussion started by: ArunJanga
3 Replies
10. Shell Programming and Scripting
Hi All,
I want to send an email if the time difference from previous mail sent is more than or equal to 30 mins.
I have written below code and it's working fine.
In this script I am storing previous mail sent time in txt file.
Instead of storing in txt file how to store in a variable.... (8 Replies)
Discussion started by: nalu
8 Replies
CoDel(8) Linux CoDel(8)
NAME
CoDel - Controlled-Delay Active Queue Management algorithm
SYNOPSIS
tc qdisc ... codel [ limit PACKETS ] [ target TIME ] [ interval TIME ] [ ecn | noecn ]
DESCRIPTION
CoDel (pronounced "coddle") is an adaptive "no-knobs" active queue management algorithm (AQM) scheme that was developed to address the
shortcomings of RED and its variants. It was developed with the following goals in mind:
o It should be parameterless.
o It should keep delays low while permitting bursts of traffic.
o It should control delay.
o It should adapt dynamically to changing link rates with no impact on utilization.
o It should be simple and efficient and should scale from simple to complex routers.
ALGORITHM
CoDel comes with three major innovations. Instead of using queue size or queue average, it uses the local minimum queue as a measure of the
standing/persistent queue. Second, it uses a single state-tracking variable of the minimum delay to see where it is relative to the stand-
ing queue delay. Third, instead of measuring queue size in bytes or packets, it is measured in packet-sojourn time in the queue.
CoDel measures the minimum local queue delay (i.e. standing queue delay) and compares it to the value of the given acceptable queue delay
target. As long as the minimum queue delay is less than target or the buffer contains fewer than MTU worth of bytes, packets are not
dropped. Codel enters a dropping mode when the minimum queue delay has exceeded target for a time greater than interval. In this mode,
packets are dropped at different drop times which is set by a control law. The control law ensures that the packet drops cause a linear
change in the throughput. Once the minimum delay goes below target, packets are no longer dropped.
Additional details can be found in the paper cited below.
PARAMETERS
limit
hard limit on the real queue size. When this limit is reached, incoming packets are dropped. If the value is lowered, packets are dropped
so that the new limit is met. Default is 1000 packets.
target
is the acceptable minimum standing/persistent queue delay. This minimum delay is identified by tracking the local minimum queue delay that
packets experience. Default and recommended value is 5ms.
interval
is used to ensure that the measured minimum delay does not become too stale. The minimum delay must be experienced in the last epoch of
length interval. It should be set on the order of the worst-case RTT through the bottleneck to give endpoints sufficient time to react.
Default value is 100ms.
ecn | noecn
can be used to mark packets instead of dropping them. If ecn has been enabled, noecn can be used to turn it off and vice-a-versa. By
default, ecn is turned off.
EXAMPLES
# tc qdisc add dev eth0 root codel
# tc -s qdisc show
qdisc codel 801b: dev eth0 root refcnt 2 limit 1000p target 5.0ms interval 100.0ms
Sent 245801662 bytes 275853 pkt (dropped 0, overlimits 0 requeues 24)
backlog 0b 0p requeues 24
count 0 lastcount 0 ldelay 2us drop_next 0us
maxpacket 7306 ecn_mark 0 drop_overlimit 0
# tc qdisc add dev eth0 root codel limit 100 target 4ms interval 30ms ecn
# tc -s qdisc show
qdisc codel 801c: dev eth0 root refcnt 2 limit 100p target 4.0ms interval 30.0ms ecn
Sent 237573074 bytes 268561 pkt (dropped 0, overlimits 0 requeues 5)
backlog 0b 0p requeues 5
count 0 lastcount 0 ldelay 76us drop_next 0us
maxpacket 2962 ecn_mark 0 drop_overlimit 0
SEE ALSO
tc(8), tc-red(8)
SOURCES
o Kathleen Nichols and Van Jacobson, "Controlling Queue Delay", ACM Queue, http://queue.acm.org/detail.cfm?id=2209336
AUTHORS
CoDel was implemented by Eric Dumazet and David Taht. This manpage was written by Vijay Subramanian. Please reports corrections to the
Linux Networking mailing list <netdev@vger.kernel.org>.
iproute2 23 May 2012 CoDel(8)