| 1 |
Adam Carter wrote: |
| 2 |
> |
| 3 |
> root@smoker / # netstat -p |
| 4 |
> Active Internet connections (w/o servers) |
| 5 |
> Proto Recv-Q Send-Q Local Address Foreign Address |
| 6 |
> State PID/Program name |
| 7 |
> tcp 0 0 192.168.1.2:43577 <http://192.168.1.2:43577> |
| 8 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 9 |
> tcp 0 0 192.168.1.2:43438 <http://192.168.1.2:43438> |
| 10 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 11 |
> tcp 0 0 192.168.1.2:52423 <http://192.168.1.2:52423> |
| 12 |
> cs204p1.msg.sp1.ya:5050 ESTABLISHED 9968/kopete |
| 13 |
> tcp 0 0 192.168.1.2:43490 <http://192.168.1.2:43490> |
| 14 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 15 |
> tcp 0 1 192.168.1.2:43586 <http://192.168.1.2:43586> |
| 16 |
> rdis.msg.vip.sp1.y:http SYN_SENT 18971/kopeteFc9968. |
| 17 |
> tcp 0 0 localhost:60971 localhost:nut |
| 18 |
> ESTABLISHED 9578/upsmon |
| 19 |
> tcp 1 1 192.168.1.2:43584 <http://192.168.1.2:43584> |
| 20 |
> rdis.msg.vip.sp1.y:http CLOSING - |
| 21 |
> tcp 0 0 192.168.1.2:43558 <http://192.168.1.2:43558> |
| 22 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 23 |
> tcp 0 0 192.168.1.2:48301 <http://192.168.1.2:48301> |
| 24 |
> cs201p1.msg.sp1.ya:5050 ESTABLISHED 9968/kopete |
| 25 |
> tcp 0 0 192.168.1.2:43523 <http://192.168.1.2:43523> |
| 26 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 27 |
> tcp 0 0 localhost:nut localhost:60971 |
| 28 |
> ESTABLISHED 9640/upsd |
| 29 |
> tcp 0 0 192.168.1.2:42517 <http://192.168.1.2:42517> |
| 30 |
> cs215p2.msg.ac4.ya:5050 ESTABLISHED 9968/kopete |
| 31 |
> tcp 0 0 192.168.1.2:43462 <http://192.168.1.2:43462> |
| 32 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 33 |
> tcp 0 0 192.168.1.2:43516 <http://192.168.1.2:43516> |
| 34 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 35 |
> tcp 0 0 192.168.1.2:43479 <http://192.168.1.2:43479> |
| 36 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 37 |
> tcp 0 0 192.168.1.2:43405 <http://192.168.1.2:43405> |
| 38 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 39 |
> tcp 0 0 192.168.1.2:43483 <http://192.168.1.2:43483> |
| 40 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 41 |
> tcp 0 0 192.168.1.2:43563 <http://192.168.1.2:43563> |
| 42 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 43 |
> tcp 0 0 192.168.1.2:43487 <http://192.168.1.2:43487> |
| 44 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 45 |
> tcp 0 0 192.168.1.2:43483 <http://192.168.1.2:43483> |
| 46 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 47 |
> tcp 0 0 192.168.1.2:43563 <http://192.168.1.2:43563> |
| 48 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 49 |
> tcp 0 0 192.168.1.2:43487 <http://192.168.1.2:43487> |
| 50 |
> rdis.msg.vip.sp1.y:http TIME_WAIT - |
| 51 |
> |
| 52 |
> One other question, if this is kopete, how does it keep |
| 53 |
> sending/receiving after I have closed the kopete app? |
| 54 |
> |
| 55 |
> Since you're closing Kopete gracefully its probably decided to let |
| 56 |
> those threads complete what they're doing before shutting them down. |
| 57 |
> If you kill -9'd them instead (that is send them the KILL signal |
| 58 |
> instead of the TERM signal) they'd go away immediately. |
| 59 |
|
| 60 |
That may be true. Thing is, it is still sending and receiving traffic |
| 61 |
even after all this time. I'm wondering what it is or if it is a bug or |
| 62 |
something. |
| 63 |
|
| 64 |
I just did a killall kopete and it did stop. Is there a way to "see" |
| 65 |
what it is sending/receiving? I'm talking like is it a jpeg, some other |
| 66 |
file or something else? |
| 67 |
|
| 68 |
Dale |
| 69 |
|
| 70 |
:-) :-) |
Archives