From owner-freebsd-bugs Sun Sep 24 22:50: 7 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 197FB37B43C for ; Sun, 24 Sep 2000 22:50:01 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id WAA55104; Sun, 24 Sep 2000 22:50:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from monkeys.com (236.dsl9226.rcsis.com [63.92.26.236]) by hub.freebsd.org (Postfix) with ESMTP id 08D9B37B42C for ; Sun, 24 Sep 2000 22:40:42 -0700 (PDT) Received: (from rfg@localhost) by monkeys.com (8.9.3/8.9.3) id WAA05191; Sun, 24 Sep 2000 22:40:35 -0700 (PDT) Message-Id: <200009250540.WAA05191@monkeys.com> Date: Sun, 24 Sep 2000 22:40:35 -0700 (PDT) From: "Ronald F. Guilmette" Reply-To: rfg@monkeys.com (Ronald F. Guilmette) To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/21531: csh/tcsh provide no way to see/adjust new socket buffer limit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 21531 >Category: bin >Synopsis: csh/tcsh provide no way to see/adjust new socket buffer limit >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Sep 24 22:50:00 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Ronald F. Guilmette >Release: FreeBSD 4.1-RELEASE i386 >Organization: Infinite Monkeys & Co. >Environment: Shell: /bin/csh or /bin/tcsh >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. >How-To-Repeat: csh -c limit >Fix: Use /bin/sh instead or only run programs that do direct calls to getrlimit/setrlimit themselves. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message