> root@smoker / # netstat -p > Active Internet connections (w/o servers) > Proto Recv-Q Send-Q Local Address Foreign Address State > PID/Program name > tcp 0 0 192.168.1.2:43577 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 192.168.1.2:43438 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 192.168.1.2:52423 cs204p1.msg.sp1.ya:5050 > ESTABLISHED 9968/kopete > tcp 0 0 192.168.1.2:43490 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 1 192.168.1.2:43586 rdis.msg.vip.sp1.y:http > SYN_SENT 18971/kopeteFc9968. > tcp 0 0 localhost:60971 localhost:nut > ESTABLISHED 9578/upsmon > tcp 1 1 192.168.1.2:43584 rdis.msg.vip.sp1.y:http > CLOSING - > tcp 0 0 192.168.1.2:43558 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 192.168.1.2:48301 cs201p1.msg.sp1.ya:5050 > ESTABLISHED 9968/kopete > tcp 0 0 192.168.1.2:43523 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 localhost:nut localhost:60971 > ESTABLISHED 9640/upsd > tcp 0 0 192.168.1.2:42517 cs215p2.msg.ac4.ya:5050 > ESTABLISHED 9968/kopete > tcp 0 0 192.168.1.2:43462 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 192.168.1.2:43516 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 192.168.1.2:43479 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 192.168.1.2:43405 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 192.168.1.2:43483 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 192.168.1.2:43563 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 192.168.1.2:43487 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 192.168.1.2:43483 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 192.168.1.2:43563 rdis.msg.vip.sp1.y:http > TIME_WAIT - > tcp 0 0 192.168.1.2:43487 rdis.msg.vip.sp1.y:http > TIME_WAIT - > > One other question, if this is kopete, how does it keep sending/receiving > after I have closed the kopete app? > > Since you're closing Kopete gracefully its probably decided to let those threads complete what they're doing before shutting them down. If you kill -9'd them instead (that is send them the KILL signal instead of the TERM signal) they'd go away immediately.