summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorwiz <wiz>2015-04-25 11:31:01 +0000
committerwiz <wiz>2015-04-25 11:31:01 +0000
commit77b23dbe06a50ffaa438f240cdae34505f0874e1 (patch)
treeb1d864e8dc8b4989e5c0c7fb6482ecca64e91496
parent86110c5d75f93d833ca0f0759f7d18af1f039316 (diff)
downloadpkgsrc-77b23dbe06a50ffaa438f240cdae34505f0874e1.tar.gz
Update documentation for UNLIMIT_RESOURCES.
-rw-r--r--doc/guide/files/fixes.xml7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/guide/files/fixes.xml b/doc/guide/files/fixes.xml
index b5672926e14..264809d648c 100644
--- a/doc/guide/files/fixes.xml
+++ b/doc/guide/files/fixes.xml
@@ -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 @@ of functions.</para>
<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