Date: Mon, 3 Dec 2007 17:35:36 -0600 (CST) From: Wes Morgan <morganw@chemikals.org> To: freebsd-ports@freebsd.org Subject: Re: How to get portinstall to 'shut up' so I can run it in background Message-ID: <alpine.BSF.0.99999.0712031734460.37247@ibyngvyr.purzvxnyf.bet> In-Reply-To: <20071203231312.GA1449@ted.stsp.lan> References: <20071128013623.GA48799@belle.0lsen.net> <475488D8.2090301@FreeBSD.org> <20071203231312.GA1449@ted.stsp.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.0.99999.0712031734460.37247>