Bug 21531

Summary: csh/tcsh provide no way to see/adjust new socket buffer limit
Product: Base System Reporter: Ronald F. Guilmette <rfg>
Component: binAssignee: Mark Peek <mp>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.1-RELEASE   
Hardware: Any   
OS: Any   

Description Ronald F. Guilmette 2000-09-25 06:50:00 UTC
	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.

Fix: 

Use /bin/sh instead or only run programs that do direct calls to
	getrlimit/setrlimit themselves.
How-To-Repeat: 
	csh -c limit
Comment 1 Bruce Evans 2000-09-25 21:52:08 UTC
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
Comment 2 Mark Peek freebsd_committer freebsd_triage 2002-07-07 17:22:05 UTC
Responsible Changed
From-To: freebsd-bugs->mp

I'll close this after the next tcsh import.
Comment 3 Mark Peek freebsd_committer freebsd_triage 2002-08-10 19:18:31 UTC
State Changed
From-To: open->closed

Fixed in tcsh-6.12.00.