From owner-freebsd-ports@FreeBSD.ORG Mon Mar 9 23:11:31 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E97BEA7 for ; Mon, 9 Mar 2015 23:11:31 +0000 (UTC) Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E3871EA for ; Mon, 9 Mar 2015 23:11:31 +0000 (UTC) Received: by iecrl12 with SMTP id rl12so25132856iec.5 for ; Mon, 09 Mar 2015 16:11:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=rUEctxPjFkBH28I2nOhjeu2hGhJAuFV6sFzKicW7g9U=; b=bqpFlu5BSLxrBBeuGPcPTvWIs7tftqeMag13CJAL9BlmBHAfyEjaA0HZxx17UeOWx0 CYzw7/jLenjAPRwyl7gzm9WDm3o4D68bKOJpE+I/wDRurWhZ3klkwQ76Wj7hP79nB23B O0O5SYxndOTF4z4Pp2psaGpY1W2J4+vygivd4eKOv8G612zj/MuINsQ7JP42Dpejwt/b IeiOljkWSFao3ZT9IuTPVLGnylrqdl5teYMTbw+o/u3YTAiVlkfMs4+tIpQYik0AxxRY GCoMuwi+d4avSEzG9CyZqrYzgx67EvGFAkt4t+RcprTGlinqLi8JH6xD33FIKanuWP6F cjhg== MIME-Version: 1.0 X-Received: by 10.107.41.83 with SMTP id p80mr51578157iop.54.1425942690444; Mon, 09 Mar 2015 16:11:30 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.174.86 with HTTP; Mon, 9 Mar 2015 16:11:30 -0700 (PDT) In-Reply-To: <54FD82A7.6040905@infracaninophile.co.uk> References: <54FB7119.4030208@FreeBSD.org> <54FD7FEC.5080500@FreeBSD.org> <54FD82A7.6040905@infracaninophile.co.uk> Date: Mon, 9 Mar 2015 16:11:30 -0700 X-Google-Sender-Auth: NlqGyB2cATalF48hsoe6VoTZByM Message-ID: Subject: Re: How could I increase "runaway" timer for package build cluster? From: Kevin Oberman To: Matthew Seaman Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Ports ML X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 23:11:31 -0000 On Mon, Mar 9, 2015 at 4:23 AM, Matthew Seaman < m.seaman@infracaninophile.co.uk> wrote: > On 03/09/15 11:11, Lev Serebryakov wrote: > > On 08.03.2015 12:40, Ben Woods wrote: > >> 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 are: > > > >> # 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 > >> #MAX_EXECUTION_TIME=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 #NOHANG_TIME=7200 > > > > The problem is, it is not my cluster, but FreeBSD official cluster. I > > could not change configs of it, I could only edit Makefile of my port. > > I added a small change to make 'pkg create' emit a progress bar which > will be in pkg-1.15 -- you have to tweak some settings in pkg.conf to > enable it though. With this change I've managed to avoid poudriere > timeouts while packaging stuff with large numbers of files -- > texlive-texmf being a classic example. You can try it now by installing > net-mgmt/pkg-devel, but beware that will eventually cause all your > client machines to end up running pkg-devel too. > > Just slightly confused. Do you mean pkg-1.4.15 (now on 1.4.12) or pkg-1.5? Any idea on time-frame? -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com