|
Started by lookitskelvin on
, 5 posts
by 4 people.
Answer Snippets (Read the full thread at reddit):
I can't read." If you start watching this at the wrong moment, it looks like a penis begins to poke out from under his chest. .
Would make a good 'motherofgod' gif "Um...I thought I told you .
S gh ....alright, look.
|
|
Okay, this is creeping me out - I see about 1500-2500 of these:
root@wherever:# netstat Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 localhost:60930 localhost:sunrpc TIME_WAIT tcp 0 0 localhost:60934 localhost:sunrpc TIME_WAIT tcp 0...
Started by KTamas on
, 5 posts
by 5 people.
Answer Snippets (Read the full thread at serverfault):
TIME_WAIT may have got lost....
It's probably harmless.
The TIME_WAIT state is what a socket goes into when "lsof -i" to see who has those sockets open and see what's doing it.
Connections (1500-2500 of them every 2-4 minutes).
|
|
What do wait time, lagged, customer, and dead mean on an agent time detailed report?
Started by ishaemc on
, 3 posts
by 3 people.
Answer Snippets (Read the full thread at net):
Dead - Total time the agent spends....
Wait - Total Time the agent has been waiting for a call
Lagged - Time that the agent client has)
Customer - Total time actually spent conversing with the customer on a live call.
|
Ask your Facebook Friends
|
The proc(5) manpage describes iowait as "time waiting for IO to complete". This was mostly explained in an earlier question. My question is: while waiting in blocking IO, does this include waiting on blocking network IO, or only local IO?
Started by Alex Jurkiewicz on
, 3 posts
by 3 people.
Answer Snippets (Read the full thread at serverfault):
It means waiting probably counts time....
However, it will include time spent waiting for network file systems like NFS.
As far.
The iowait time is the amount of time a process spends in the kernel I/O scheduler.
|
|
I was reading about using the SO_LINGER socket option to intentionally 'assassinate' the time-wait state by setting the linger time to zero. The author of the book then goes on to say we should never do this and in general that we should never interfere...
Started by Robert S. Barnes on
, 3 posts
by 3 people.
Answer Snippets (Read the full thread at stackoverflow):
In TIME_WAIT you are just waiting for any stray packets to arrive at the local address.
It occurs after a TCP FIN on the local side followed by a TCP FIN ACK from the remote location .
TIME_WAIT is absolutely normal.
|
|
Is there a vmstat type command that works per-process that allows you to see how much time a process is blocked waiting for I/O , time in kernel and user code?
Started by Readonly on
, 5 posts
by 5 people.
Answer Snippets (Read the full thread at stackoverflow):
Strace will show you how much time is spent in system call, however it won't tell you how much of this time is spent in waiting....
For, block layer information, wait/blocking/busy etc..., very in depth, there are quite a few.
|
|
This is my first time posting here (besides my intro), and I'm having a similar problem with two friends: constant lateness.
The first has 3 children, a home business and a very busy life. Over the last year, she's gone from occasionally late to always...
Started by dharmaexpress on
, 15 posts
by 10 people.
Answer Snippets (Read the full thread at etiquettehell):
To travel WITH her anymore.
|
|
How do you tell a Ruby program to wait an arbitrary amount of time before moving on to the next line of code?
thanks
Answer Snippets (Read the full thread at stackoverflow):
(This is useful when you want a thread to sleep until it's woken.)
It's pretty easy:
sleep(num_secs... .
If you just run sleep , the process will sleep forever .
Be careful to give an argument.
Sleep
Use sleep like so:
sleep 2
That'll sleep for 2 seconds .
|
|
Question about the MAC-protocol of 802.11 Wifi.
We have learned that when a station has received the data it waits for SIFS time. Then it sends the packet. When searching online the reason that is always mentioned is to give ACK packets a higher priority...
Started by Omega on
, 4 posts
by 4 people.
Answer Snippets (Read the full thread at stackoverflow):
Rather than the server sending back 400 ACKs, it can simply wait until the client-before time....
As long as the wait-before-sending-ack time on the receiver is less than the retransmit-if-no-ack to the server.
Such a strategy.
|
|
Is there a linux command that allows you to see a processes IO wait time vs. CPU time? I'm trying to see whether some processes are IO-bound or CPU-bound.
Started by ro on
, 6 posts
by 6 people.
Answer Snippets (Read the full thread at serverfault):
Top (1) will....
I am not sure how you see the I/O stats for a particular process .
Simply using top should give let you know if the a particular process is CPU or memory bound .
If you install the atsar package you can look at the system's CPU and I/O stats .
|