[pkgsrc/trunk]: pkgsrc/doc/guide/files Update documentation for UNLIMIT_RESOU...

[wiz <wiz%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/1d0637ee2e87
branches:  trunk
changeset: 650644:1d0637ee2e87
user:      wiz <wiz%pkgsrc.org@localhost>
date:      Sat Apr 25 11:31:01 2015 +0000

description:
Update documentation for UNLIMIT_RESOURCES.

diffstat:

 doc/guide/files/fixes.xml |  7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)

diffs (21 lines):

diff -r c5569cc427cb -r 1d0637ee2e87 doc/guide/files/fixes.xml
--- a/doc/guide/files/fixes.xml Sat Apr 25 11:28:08 2015 +0000
+++ b/doc/guide/files/fixes.xml Sat Apr 25 11:31:01 2015 +0000
@@ -1,4 +1,4 @@
-<!-- $NetBSD: fixes.xml,v 1.130 2015/03/07 21:31:15 tnn Exp $ -->
+<!-- $NetBSD: fixes.xml,v 1.131 2015/04/25 11:31:01 wiz Exp $ -->
 
 <chapter id="fixes"> <?dbhtml filename="fixes.html"?>
 <title>Making your package work</title>
@@ -1366,8 +1366,9 @@
     <para>Sometimes packages fail to build because the compiler runs
     into an operating system specific soft limit.  With the
     <varname>UNLIMIT_RESOURCES</varname> variable pkgsrc can be told
-    to unlimit the resources.  Currently, the allowed values are
-    <quote>datasize</quote> and <quote>stacksize</quote> (or both).
+    to unlimit the resources.  Currently, the allowed values are any combination of
+    <quote>cputime</quote>, <quote>datasize</quote>,
+    <quote>memorysize</quote>, and <quote>stacksize</quote>.
     Setting this variable is similar to running the shell builtin
     <command>ulimit</command> command to raise the maximum data
     segment size or maximum stack size of a process, respectively, to