From owner-freebsd-current Sun Jan 7 14:30:21 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 5097E37B400 for ; Sun, 7 Jan 2001 14:30:03 -0800 (PST) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id PAA21514; Sun, 7 Jan 2001 15:30:02 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id PAA06937; Sun, 7 Jan 2001 15:30:01 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14936.60905.340826.334042@nomad.yogotech.com> Date: Sun, 7 Jan 2001 15:30:01 -0700 (MST) To: Archie Cobbs Cc: current@FreeBSD.ORG Subject: Re: weird cvs update problem In-Reply-To: <200101072123.f07LNCB43746@curve.dellroad.org> References: <200101070126.f071QT512153@vashon.polstra.com> <200101072123.f07LNCB43746@curve.dellroad.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > U crypto/kerberosIV/appl/bsd/login_fbtab.c > > > > U crypto/kerberosIV/appl/bsd/osfc2.c > > > > U crypto/kerberosIV/appl/bsd/pathnames.h_ > > > > U crypto/kerberosIV/appl/bsd/rcmd_util.c > > > > cvs update: warning: unrecognized response ` If there are any IP options on `sock', die.' from cvs server > > > > cvs update: warning: unrecognized response ` */' from cvs server > > [...] > > > > It sounds like maybe the rcmd_util.c,v RCS file is corrupted on the > > CVS server. Just a guess. I haven't seen the problem here. > > Don't think so.. this happens rather randomly for random files > (i.e., more than one). The same file will update correctly on the > second try (but then it barfs on another one). > > It doesn't seem to happen for patched files, only for files that > are downloaded whole.. ie, if you blow away an entire directory > and then download it again. Just a question. Are you using any sort of transport mechanism (besides rsh) in the middle? I had problems like this when using F-Secure's Windows client using compression, which blew up. We switched the users to SecureCRT and the problems went away. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message