From owner-freebsd-ports@FreeBSD.ORG Mon Dec 3 23:57:54 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18BAB16A41A for ; Mon, 3 Dec 2007 23:57:54 +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 CC79B13C465 for ; Mon, 3 Dec 2007 23:57:53 +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 lB3NZall000223 for ; Mon, 3 Dec 2007 18:35:37 -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 lB3NZavE071589 for ; Mon, 3 Dec 2007 17:35:36 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Mon, 3 Dec 2007 17:35:36 -0600 (CST) From: Wes Morgan To: freebsd-ports@freebsd.org In-Reply-To: <20071203231312.GA1449@ted.stsp.lan> Message-ID: References: <20071128013623.GA48799@belle.0lsen.net> <475488D8.2090301@FreeBSD.org> <20071203231312.GA1449@ted.stsp.lan> User-Agent: Alpine 0.99999 (BSF 796 2007-11-08) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII 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: Mon, 03 Dec 2007 23:57:54 -0000 On Tue, 4 Dec 2007, Stefan Sperling wrote: > On Mon, Dec 03, 2007 at 02:53:12PM -0800, Doug Barton wrote: >> 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. >> >> While I know screen(1) has a lot of devotees, you could almost >> certainly use nohup for this same purpose, with the pleasant side >> effect that you will have a log of what happened on disk in case >> something blows up. > > Screen also has log functionality. > Toggle with: Ctrl+A, then Shift+H You can also use "script" to capture the output fairly easily.