|
|
Sponsored Content
Top Forums
UNIX for Advanced & Expert Users
Time_wait ??
Post 18086 by shibz on Saturday 23rd of March 2002 05:21:26 AM
03-23-2002
|
|
5 More Discussions You Might Find Interesting
1. IP Networking
Why would I get TIME_WAIT when i netstat a port?? What would be some scenarios of this situation?? (1 Reply)
Discussion started by: eloquent99
1 Replies
2. UNIX for Advanced & Expert Users
What is the maximum number of TCP ports that can be consumed at any one time? How can I determine what the number is or increase it?
I was under the impression that with our system (UnixWare 7.1.1) 1024 was the maximum under our current Kernel tuning parms, but I think that is really just... (4 Replies)
Discussion started by: dlkox
4 Replies
3. UNIX for Advanced & Expert Users
in TCP, is TIME_WAIT state really essential..!!! (3 Replies)
Discussion started by: sasikanth
3 Replies
4. Red Hat
Hi,
I want to kill TCP connections which have status as TIME_WAIT & no PID
(as per the output of the "netstat - p" command).
Is there any command/utility available to kill connections to a specific port or IP address.
The problem is that these connections don't have process ID (see... (4 Replies)
Discussion started by: Davinder31may
4 Replies
5. UNIX for Dummies Questions & Answers
Server has more TIME_WAIT connections in Apache(port 80) Hi,
My webserver has 16GB of RAM and CentOS 5.5, Apache 2.2.3, It's shared webserver used of for webhosting. I have optmized the server as :
<IfModule prefork.c>... (4 Replies)
Discussion started by: chandranjoy
4 Replies
LEARN ABOUT ULTRIX
ruptime
ruptime(1c) ruptime(1c) Name ruptime - show host status of local machines Syntax ruptime [ options ] [ machinename ] Description The command gives a status line like for each machine on the local network. If a machinename is given, the status of only the named machine is given. These status lines are formed from packets broadcast by each host on the network once a minute. Machines for which no status report has been received for 5 minutes are shown as being down. Options -a Users idle an hour or more are not counted unless this option is specified. -d Display only those hosts that are considered down. -l Sort the status list by load average. If more than one sort option is given, uses the last one. -r Show only hosts that are up and running. -t Sort the status list by uptime. If more than one sort option is given, uses the last one. -u Sort the status list by number of users. If more than one sort option is given, uses the last one. -nn Show only those hosts with nn or more users. Restrictions Because the daemon sends its information in broadcast packets it generates a large amount of network traffic. On large networks the extra traffic may be objectionable. Therefore, the daemon is disabled by default. To make use of the daemon for both the local and remote hosts, remove the comment symbols (#) from in front of the lines specifying in the file. If the daemon is not running on a remote machine, the machine may incorrectly appear to be down when you use the command to determine its status. See the reference page for more information. If a system has more than 40 users logged in at once, the number of users displayed by the command is incorrect. Users who login to a machine after that point fail to increment the user count that appears in the output of the command. This is due to the maximum size limit of an Ethernet packet, which is 1500 bytes, and the fact that the daemon must broadcast its information in a single packet. Files /usr/spool/rwho/whod.* Information about other machines See Also rwho(1c), rwhod(8c) ruptime(1c)