How could I increase "runaway" timer for package build cluster?

Ben Woods woodsb02 at
Sun Mar 8 09:40:29 UTC 2015

Actually, taking a look at my /usr/local/etc/poudriere.conf configuration
file, I see these settings have indeed been exposed for configuration there
without having to touch the poudriere code itself. The appropriate settings

# This defines the max time (in seconds) that a command may run for a build
# before it is killed for taking too long. Default: 86400

# This defines the time (in seconds) before a command is considered to
# be in a runaway state for having no output on stdout. Default: 7200


From: Benjamin Woods
woodsb02 at

On 8 March 2015 at 07:00, Ben Woods <woodsb02 at> wrote:
> You can increase the max_execution_time in /usr/local/share/
(default 3600 seconds). There are individual timeout values for extract,
install, package and deinstall. These are the maximum values for each stage
(with or without output being produced).
> But more likely, you need to look at the NOHANG_TIME value in the same file (default 7200 seconds). This is the one related to having no
output produced (aka "runaway build").
> Someone has previously spoken about exposing these kinds of values for
tweaking in the poudriere configuration files, but I'm not sure it ever
> Regards,
> Ben
> On Sunday, March 8, 2015, Lev Serebryakov <lev at> wrote:
>> Hash: SHA512
>>  One of my ports (devel/gcc-arm-embedded) doesn't produce much output
>> on build (output is redirected to log files), but takes severa hours
>> to be built.
>>  Looks like pkg building cluster doesn't like such behavior.
>>  Could I notify build cluster (poudrere?) that this package takes a
>> lot of time without output?
>> - --
>> // Lev Serebryakov AKA Black Lion

More information about the freebsd-ports mailing list