summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorrillig <rillig@pkgsrc.org>2007-01-18 09:04:53 +0000
committerrillig <rillig@pkgsrc.org>2007-01-18 09:04:53 +0000
commitd817b0900c146a7d56d3ad8b76ba7b3bedefb039 (patch)
treea2f5c8b25c2b974cd55e0775bbf93c4511cc95de
parent427386059c94c306fd5f9f155f643077de90fd6b (diff)
downloadpkgsrc-d817b0900c146a7d56d3ad8b76ba7b3bedefb039.tar.gz
pkgsrc bulk builds need much CPU time, but do they also need much stack?
-rw-r--r--mk/bulk/build7
1 files changed, 4 insertions, 3 deletions
diff --git a/mk/bulk/build b/mk/bulk/build
index 83bb233e9f0..7801b8d75bd 100644
--- a/mk/bulk/build
+++ b/mk/bulk/build
@@ -1,5 +1,5 @@
#!/bin/sh
-# $NetBSD: build,v 1.97 2006/12/15 12:46:24 martti Exp $
+# $NetBSD: build,v 1.98 2007/01/18 09:04:53 rillig Exp $
#
# Copyright (c) 1999, 2000 Hubert Feyrer <hubertf@NetBSD.org>
@@ -200,8 +200,9 @@ do_common_setup () {
#
# Set resource limits as high as possible
#
- ulimit -S -s `ulimit -H -s`
- ulimit -S -d `ulimit -H -d`
+ ulimit -S -s `ulimit -H -s` # XXX: why do we need unlimited stack?
+ ulimit -S -d `ulimit -H -d` # some processes grow rather large
+ ulimit -S -t `ulimit -H -t` # pkgsrc bulk builds need _much_ time
#
# Find the configuration file.