From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ol9Hn-0001xD-SR for garchives@archives.gentoo.org; Mon, 16 Aug 2010 23:40:12 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1C0F0E08E8; Mon, 16 Aug 2010 23:39:27 +0000 (UTC) Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181]) by pigeon.gentoo.org (Postfix) with ESMTP id B919CE08E8 for ; Mon, 16 Aug 2010 23:39:26 +0000 (UTC) Received: by wyf28 with SMTP id 28so7674231wyf.40 for ; Mon, 16 Aug 2010 16:39:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=Mb72E2/V3wMImnIgI4EXfGSF307FDgi2lQnYFcdpCvg=; b=B+rfj0Coj4LUG9FgU/OVDlQH8IULtwKrzS39yjX4WIEpF+bH5R/84HIexuuINA+eFL XK29VbwivzeyujFhzVhH+ZKSBULShQ6mqqFrhgLnpWms9EkgeXsn79J2Z/JOatL0wHPY Wg/NUoO9Gr9+51zN6lm1ibHB6FwbpWXym2P/U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=oQOlJPf3tGL7GCkoVecDxDsvskMm85afjanplPpxV8PlgkFWRwaKviqdPxIBcrMsPq Y6HhleiYO4clDt5xhucDLXBJYrNhDd4AV8mFkdbKMoJtQn3aX5TwoGr19AbyjZ5uz9lt 7bOzsC/mCJyrYDeGH38ExJOOaA+GP4Tqw5YXg= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.216.236.42 with SMTP id v42mr92785weq.10.1282001966155; Mon, 16 Aug 2010 16:39:26 -0700 (PDT) Received: by 10.216.1.199 with HTTP; Mon, 16 Aug 2010 16:39:26 -0700 (PDT) In-Reply-To: <4C69C1E4.9090309@gmail.com> References: <4C684F59.3040903@gmail.com> <201008152329.44195.alan.mckinnon@gmail.com> <4C69C1E4.9090309@gmail.com> Date: Tue, 17 Aug 2010 09:39:26 +1000 Message-ID: Subject: Re: [gentoo-user] Yahoo and strange traffic. From: Adam Carter To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=000e0cd4d40ccb4945048df957d6 X-Archives-Salt: 02dfa4aa-d3fa-4aef-96be-ca8c620a8f18 X-Archives-Hash: 8b9485363bbad807244e80f1b10783f3 --000e0cd4d40ccb4945048df957d6 Content-Type: text/plain; charset=ISO-8859-1 > 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. --000e0cd4d40ccb4945048df957d6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
root@smoker / # netstat -p
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address =A0 =A0 =A0 =A0 =A0 Foreign Address =A0 = =A0 =A0 =A0 State =A0 =A0 =A0 PID/Program name
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43577 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43438 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:52423 =A0 =A0 =A0 cs204p1.msg.sp1.ya:5050 EST= ABLISHED 9968/kopete
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43490 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A01 192.168.1.2:43586 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http SYN= _SENT =A0 =A018971/kopeteFc9968.
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 localhost:60971 =A0 =A0 =A0 =A0 localhost= :nut =A0 =A0 =A0 =A0 =A0 ESTABLISHED 9578/upsmon
tcp =A0 =A0 =A0 =A01 =A0 =A0 =A01 192.168.1.2:43584 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http CLO= SING =A0 =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43558 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:48301 =A0 =A0 =A0 cs201p1.msg.sp1.ya:5050 EST= ABLISHED 9968/kopete
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43523 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 localhost:nut =A0 =A0 =A0 =A0 =A0 localho= st:60971 =A0 =A0 =A0 =A0 ESTABLISHED 9640/upsd
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:42517 =A0 =A0 =A0 cs215p2.msg.ac4.ya:5050 EST= ABLISHED 9968/kopete
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43462 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43516 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43479 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43405 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43483 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43563 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43487 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43483 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43563 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -
tcp =A0 =A0 =A0 =A00 =A0 =A0 =A00 192.168.1.2:43487 =A0 =A0 =A0 rdis.msg.vip.sp1.y:http TIM= E_WAIT =A0 -

One other question, if this is kopete, how does it keep sending/receiving a= fter I have closed the kopete app?

Since you're closing Kopete gracefully its probab= ly decided to let those threads complete what they're doing before shut= ting them down. If you kill -9'd them instead (that is send them the KI= LL signal instead of the TERM signal) they'd go away immediately.
--000e0cd4d40ccb4945048df957d6--