From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 14 11:35:13 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 35F7C621 for ; Thu, 14 Feb 2013 11:35:13 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id D9381AAB for ; Thu, 14 Feb 2013 11:35:12 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa03.fnfis.com (8.14.5/8.14.5) with ESMTP id r1EBZ76p022418 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 14 Feb 2013 05:35:12 -0600 Received: from LTCFISWMSGMB21.FNFIS.com ([10.132.99.23]) by LTCFISWMSGHT04.FNFIS.com ([10.132.206.15]) with mapi id 14.02.0309.002; Thu, 14 Feb 2013 05:34:26 -0600 From: "Teske, Devin" To: Wojciech Puchar Subject: RE: rsh/rlogin strange behavior Thread-Topic: rsh/rlogin strange behavior Thread-Index: AQHOCp9xD1iNtGIRjUuq20A96tJlfZh5L3kpgABs94D//5u9bw== Date: Thu, 14 Feb 2013 11:34:25 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D7201EA941E@ltcfiswmsgmb21> References: , <13CA24D6AB415D428143D44749F57D7201EA93B6@ltcfiswmsgmb21>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.120] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327, 1.0.431, 0.0.0000 definitions=2013-02-14_04:2013-02-14,2013-02-14,1970-01-01 signatures=0 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Feb 2013 11:35:13 -0000 On Thu, 14 Feb 2013, Wojciech Puchar wrote: > it is FreeBSD 9, em or re or bge hardware but rlogin goes over tun(4) > interface. >=20 > in the same time rcp works fine even for gigabyte file. >=20 > any more ideas? Try to isolate the problem as network or disk or other... systat -iostat 1 netstat 1 systat -vmstat 1 NOTE: Don't forget systat takes ":ignore " which can be handy at ti= mes if you have a lot of devices Those are a good start. Others can offer others to see where your data is c= hoking. HINT: Look for errors in the "netstat 1" output? --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.