Re: weird cvs update problem
On Sun, 7 Jan 2001, Archie Cobbs wrote: John Polstra 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. Since the new version CVS appears to have random problems. Is used to have a command like find . -type f | grep -v CVS | xargs cvs status | ... in my Makefiles, but this does not work anymore. The cvs fails in random ways with different error messages. Using cvs status with only one file name works most of the time, but can be really slow when you have a large tree. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
ISTR Christian Weisgerber [EMAIL PROTECTED] was having this problem
too.
I don't know if there was any fix as such
I have a -current system from Dec. 7 on which I'm trying to do
a cvs update in preparation of make world, and am seeing wierd
stuff like this:
cvs server: Updating crypto/kerberosIV/appl/afsutil
U crypto/kerberosIV/appl/afsutil/Makefile.in
U crypto/kerberosIV/appl/afsutil/aklog.c
U crypto/kerberosIV/appl/afsutil/kstring2key.c
U crypto/kerberosIV/appl/afsutil/pagsh.c
cvs server: Updating crypto/kerberosIV/appl/bsd
U crypto/kerberosIV/appl/bsd/Makefile.in
U crypto/kerberosIV/appl/bsd/README.login
U crypto/kerberosIV/appl/bsd/bsd_locl.h
U crypto/kerberosIV/appl/bsd/encrypt.c
U crypto/kerberosIV/appl/bsd/forkpty.c
U crypto/kerberosIV/appl/bsd/kcmd.c
U crypto/kerberosIV/appl/bsd/klogin.c
U crypto/kerberosIV/appl/bsd/krcmd.c
U crypto/kerberosIV/appl/bsd/login.c
U crypto/kerberosIV/appl/bsd/login_access.c
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
cvs update: warning: unrecognized response `' from cvs server
cvs update: warning: unrecognized response `void' from cvs server
cvs update: warning: unrecognized response `ip_options_and_die (int sock, struct
sockaddr_in *fromp)' from cvs server
cvs update: warning: unrecognized response `{' from cvs server
cvs update: warning: unrecognized response `#if defined(IP_OPTIONS)
defined(HAVE_GETSOCKOPT)' from cvs server
cvs update: warning: unrecognized response ` u_char optbuf[BUFSIZ/3], *cp;' from
cvs server
cvs update: warning: unrecognized response ` char lbuf[BUFSIZ], *lp;' from cvs
server
The file data is somehow getting mixed into the "control stream"
or something. The cvs server is a 5.0-2506-CURRENT machine
that has been working fine for many months (and I don't see the
same problem when cvs updating from other machines).
I notice that "cvs" was updated to version 1.11 on 10/31/00...
Has anyone else seen this, and if so, what's the fix??
Thanks,
-Archie
__
Archie Cobbs * Packet Design * http://www.packetdesign.com
--
Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org
http://www.Awfulhak.org brian@[uk.]OpenBSD.org
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
John Polstra 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. -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
Brian Somers [EMAIL PROTECTED] wrote: ISTR Christian Weisgerber [EMAIL PROTECTED] was having this problem too. Sorry, you're misremembering. I've never seen anything like this. -- Christian "naddy" Weisgerber [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
Brian Somers [EMAIL PROTECTED] wrote: ISTR Christian Weisgerber [EMAIL PROTECTED] was having this problem too. Sorry, you're misremembering. I've never seen anything like this. You're right you know - my apologies ! -- Christian "naddy" Weisgerber [EMAIL PROTECTED] -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird cvs update problem
In article [EMAIL PROTECTED], Archie Cobbs [EMAIL PROTECTED] wrote: I have a -current system from Dec. 7 on which I'm trying to do a cvs update in preparation of make world, and am seeing wierd stuff like this: cvs server: Updating crypto/kerberosIV/appl/afsutil U crypto/kerberosIV/appl/afsutil/Makefile.in U crypto/kerberosIV/appl/afsutil/aklog.c U crypto/kerberosIV/appl/afsutil/kstring2key.c U crypto/kerberosIV/appl/afsutil/pagsh.c cvs server: Updating crypto/kerberosIV/appl/bsd U crypto/kerberosIV/appl/bsd/Makefile.in U crypto/kerberosIV/appl/bsd/README.login U crypto/kerberosIV/appl/bsd/bsd_locl.h U crypto/kerberosIV/appl/bsd/encrypt.c U crypto/kerberosIV/appl/bsd/forkpty.c U crypto/kerberosIV/appl/bsd/kcmd.c U crypto/kerberosIV/appl/bsd/klogin.c U crypto/kerberosIV/appl/bsd/krcmd.c U crypto/kerberosIV/appl/bsd/login.c U crypto/kerberosIV/appl/bsd/login_access.c 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. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
