>Number:         9068
>Category:       kern
>Synopsis:       some VM-related updates for options(4)
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 28 18:33:01 1999
>Last-Modified:
>Originator:     Greg A. Woods
>Organization:
Planix, Inc.; Toronto, Ontario; Canada
>Release:        NetBSD-current
>Environment:

>Description:

	here are some minor updates for options(4), including a couple
	of wee fixes as well as new entries for some of the tunable
	values in sys/arch/*/include/vmparam.h

>How-To-Repeat:

	look at sys/arch/*/include/vmparam.h and look for tunable items
	in options(4)....

>Fix:

Index: options.4
===================================================================
RCS file: /cvs/NetBSD/src/share/man/man4/options.4,v
retrieving revision 1.1.1.6
diff -c -c -r1.1.1.6 options.4
*** options.4	1998/11/16 20:50:09	1.1.1.6
--- options.4	1999/12/29 02:23:42
***************
*** 502,508 ****
  Includes code for the Coda file system.
  Coda is a distributed file system like NFS and AFS.  It is
  freely available, like NFS, but it functions much like AFS in being a
! "stateful" file system.  Both Coda and AFS cache files on your local
  machine to improve performance.  Then Coda goes a step further than AFS
  by letting you access the cached files when there is no available
  network, viz. disconnected laptops and network outages.  In Coda, both
--- 502,508 ----
  Includes code for the Coda file system.
  Coda is a distributed file system like NFS and AFS.  It is
  freely available, like NFS, but it functions much like AFS in being a
! ``stateful'' file system.  Both Coda and AFS cache files on your local
  machine to improve performance.  Then Coda goes a step further than AFS
  by letting you access the cached files when there is no available
  network, viz. disconnected laptops and network outages.  In Coda, both
***************
*** 816,827 ****
  driver,
  and much of the networking code.
  .It Cd options MAXUPRC=integer
! Sets the
! .Em RLIMIT_NPROC
! resource limit, which specifies the maximum number of simultaneous
! processes a user is permitted to run, for process 0;
! this value is inherited by its child processes.
! It defaults to
  .Em CHILD_MAX ,
  which is currently defined to be 80.
  Setting
--- 816,828 ----
  driver,
  and much of the networking code.
  .It Cd options MAXUPRC=integer
! Sets the soft
! .Dv RLIMIT_NPROC
! resource limit (as returned by
! .Xr getrlimit 2 )
! for process 0; which specifies the maximum number of simultaneous
! processes a user is permitted to run.  This value is inherited by all
! child processes.  It defaults to
  .Em CHILD_MAX ,
  which is currently defined to be 80.
  Setting
***************
*** 831,837 ****
  is not permitted, as this would result in a violation of the semantics of
  .St -p1003.1-90 .
  .It Cd options SHORTCORENAME
! If set, process core dumps are named 
  .Nm core .
  If not specified, they are named
  .Nm programname.core 
--- 832,838 ----
  is not permitted, as this would result in a violation of the semantics of
  .St -p1003.1-90 .
  .It Cd options SHORTCORENAME
! If set, process core dumps are named
  .Nm core .
  If not specified, they are named
  .Nm programname.core 
***************
*** 1164,1169 ****
--- 1165,1211 ----
  Their default value is a machine dependent value, often calculated as
  between 5% and 10% of total available
  .Tn RAM .
+ .It Cd options MAXTSIZ=bytes
+ Sets the maximum size limit of a process' text segment.  The default
+ value varies from 6MB to 1GB depending on the port.  See
+ .Pa /usr/include/machine/vmparam.h
+ for the architecture specific default.
+ .It Cd options DFLDSIZ=bytes
+ Sets the default size limit of a process' data segment, the value that
+ will be returned as the soft limit for
+ .Dv RLIMIT_DATA
+ (as returned by
+ .Xr getrlimit 2 ).
+ The default value varies from 16MB to 128MB depending on the port.  See
+ .Pa /usr/include/machine/vmparam.h
+ for the architecture specific default.
+ .It Cd options MAXDSIZ=bytes
+ Sets the maximum size limit of a process' data segment, the value that
+ will be returned as the hard limit for
+ .Dv RLIMIT_DATA
+ (as returned by
+ .Xr getrlimit 2 ).
+ The default value varies from 24MB to 1GB depending on the port.  See
+ .Pa /usr/include/machine/vmparam.h
+ for the architecture specific default.
+ .It Cd options DFLSSIZ=bytes
+ Sets the default size limit of a process' stack segment, the value that
+ will be returned as the soft limit for
+ .Dv RLIMIT_STACK
+ (as returned by
+ .Xr getrlimit 2 ).
+ The default value varies from 512KB to 2MB depending on the port.  See
+ .Pa /usr/include/machine/vmparam.h
+ for the architecture specific default.
+ .It Cd options MAXSSIZ=bytes
+ Sets the maximum size limit of a process' stack segment, the value that
+ will be returned as the hard limit for
+ .Dv RLIMIT_STACK
+ (as returned by
+ .Xr getrlimit 2 ).
+ The default value varies from 8MB to 64MB depending on the port.  See
+ .Pa /usr/include/machine/vmparam.h
+ for the architecture specific default.
  .El
  .Ss amiga-specific Options
  .Bl -ohang
***************
*** 1389,1394 ****
--- 1431,1437 ----
  .Sh SEE ALSO
  .Xr config 8 ,
  .Xr init 8 ,
+ .Xr getrlimit 2 ,
  .Xr gettimeofday 2 ,
  .Xr sysctl 8 ,
  .Xr sysctl 3 ,
>Audit-Trail:
>Unformatted: