From owner-freebsd-current Thu Aug 31 5:45:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 3277637B422; Thu, 31 Aug 2000 05:45:37 -0700 (PDT) Received: from modemcable136.203-201-24.mtl.mc.videotron.net ([24.201.203.136]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G05002WBQ16QW@field.videotron.net>; Thu, 31 Aug 2000 08:43:54 -0400 (EDT) Date: Thu, 31 Aug 2000 08:47:14 -0400 (EDT) From: Bosko Milekic Subject: Re: cvs commit: src/sys/kern uipc_socket2.c In-reply-to: <200008310612.e7V6C9m00286@wint.itfs.nsk.su> X-Sender: bmilekic@jehovah.technokratis.com To: Nickolay Dudorov Cc: current@FreeBSD.ORG, Brian Feldman Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Uh-oh. Could this have something to do with the fact that Brian passes `cc' to chgsbsize(), which declares it as a u_long, when in fact it should be handled as an rlim_t, which is really a 64-bit integer? I'm not too sure, as I didn't think at first that reverting just this back would solve the problem. On Thu, 31 Aug 2000, Nickolay Dudorov wrote: > In article <200008300009.RAA96392@freefall.freebsd.org> you wrote: > > green 2000/08/29 17:09:58 PDT > > > > Modified files: > > sys/kern uipc_socket2.c > > Log: > > Remove an extraneous setting of sb_hiwat. > > > > Revision Changes Path > > 1.63 +1 -2 src/sys/kern/uipc_socket2.c > > After reverting this file to rev 1.62 i can build, boot > and use my kernel. The kernels builded after yesterday's and today's > cvsup (i.e. with the 1.63 rev of sys/kern/uipc_socket2.c) hung after > ssh-ing to this system (or telnet-ting ;-). (See 'current' and 'stable' > maillists for more detailed description of the problem). > > N.Dudorov Cheers, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message