Date: Sun, 24 Sep 2000 22:40:35 -0700 (PDT) From: "Ronald F. Guilmette" <rfg@monkeys.com> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/21531: csh/tcsh provide no way to see/adjust new socket buffer limit Message-ID: <200009250540.WAA05191@monkeys.com>
next in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200009250540.WAA05191>