From owner-freebsd-ports@FreeBSD.ORG Wed Nov 28 01:56:17 2007 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3816416A468 for ; Wed, 28 Nov 2007 01:56:17 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from tiamat.relinetworks.com (tiamat.relinetworks.com [204.214.92.162]) by mx1.freebsd.org (Postfix) with ESMTP id F20BB13C467 for ; Wed, 28 Nov 2007 01:56:16 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (root@r74-193-170-223.bssrcmta01.bscyla.by.dh.suddenlink.net [74.193.170.223] (may be forged)) by tiamat.relinetworks.com (8.14.1/8.14.1) with ESMTP id lAS1fads023128; Tue, 27 Nov 2007 20:41:36 -0500 (EST) (envelope-from morganw@chemikals.org) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.2/8.14.2) with ESMTP id lAS1fYYv005519; Tue, 27 Nov 2007 19:41:35 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Tue, 27 Nov 2007 19:41:34 -0600 (CST) From: Wes Morgan To: Clint Olsen In-Reply-To: <20071128013623.GA48799@belle.0lsen.net> Message-ID: References: <20071128013623.GA48799@belle.0lsen.net> User-Agent: Alpine 0.99999 (BSF 796 2007-11-08) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: ports@freebsd.org Subject: Re: How to get portinstall to 'shut up' so I can run it in background X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2007 01:56:17 -0000 On Tue, 27 Nov 2007, Clint Olsen wrote: > I've tried redirecting standard output/error, both /bin/sh and /bin/csh, > and I can't run this in batch. I'm trying to build gnome which takes > hours, and I want it backgrounded so that if this SSH shell disconnects it > doesn't crater the build. You would think that --batch would make this > happen, but no go. Why not just run the build inside a screen session? Getting disconnected would have no effect on it then.