From owner-freebsd-bugs Mon Sep 25 14: 0: 6 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7903C37B43C for ; Mon, 25 Sep 2000 14:00:03 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id OAA63688; Mon, 25 Sep 2000 14:00:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 25 Sep 2000 14:00:03 -0700 (PDT) Message-Id: <200009252100.OAA63688@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bruce Evans Subject: Re: bin/21531: csh/tcsh provide no way to see/adjust new socket buffer limit Reply-To: Bruce Evans Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/21531; it has been noted by GNATS. From: Bruce Evans To: "Ronald F. Guilmette" Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/21531: csh/tcsh provide no way to see/adjust new socket buffer limit Date: Tue, 26 Sep 2000 07:52:08 +1100 (EST) On Sun, 24 Sep 2000, Ronald F. Guilmette wrote: > >Description: > > I see that a new limit has been added on the manpage for setrlimit(2), > i.e. one for socket buffer space. Good. Now all that's needed is > to make the csh/tcsh `limit' command aware of it, as /usr/bin/limits > alread seems to be. It was implemented in csh and clobbered by replacing csh by tcsh. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message