Date: Sun, 7 Jan 2001 14:44:01 -0800 (PST) From: Archie Cobbs <archie@dellroad.org> To: Nate Williams <nate@yogotech.com> Cc: current@FreeBSD.ORG Subject: Re: weird cvs update problem Message-ID: <200101072244.f07Mi1144150@curve.dellroad.org> In-Reply-To: <14936.60905.340826.334042@nomad.yogotech.com> "from Nate Williams at Jan 7, 2001 03:30:01 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101072244.f07Mi1144150>