From owner-freebsd-current  Sun Jan  7 14:44:19 2001
Delivered-To: freebsd-current@freebsd.org
Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26])
	by hub.freebsd.org (Postfix) with ESMTP id 858C737B400
	for <current@FreeBSD.ORG>; Sun,  7 Jan 2001 14:44:02 -0800 (PST)
Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30])
	by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id OAA54957;
	Sun, 7 Jan 2001 14:44:01 -0800 (PST)
Received: (from archie@localhost)
	by curve.dellroad.org (8.11.0/8.11.0) id f07Mi1144150;
	Sun, 7 Jan 2001 14:44:01 -0800 (PST)
	(envelope-from archie)
From: Archie Cobbs <archie@dellroad.org>
Message-Id: <200101072244.f07Mi1144150@curve.dellroad.org>
Subject: Re: weird cvs update problem
In-Reply-To: <14936.60905.340826.334042@nomad.yogotech.com> "from Nate Williams
 at Jan 7, 2001 03:30:01 pm"
To: Nate Williams <nate@yogotech.com>
Date: Sun, 7 Jan 2001 14:44:01 -0800 (PST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL82 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Nate Williams writes:
> > > > > 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.

Nope.. just using cvs in pserver mode to a server on the same subnet,
not encrypted or compressed or anything.

Once I actually get all of the -current sources I'll rebuild world
and see if the problem still exists.

-Archie

__________________________________________________________________________
Archie Cobbs     *     Packet Design     *     http://www.packetdesign.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message