From owner-freebsd-questions Sun Dec 10 18:12: 8 2000 From owner-freebsd-questions@FreeBSD.ORG Sun Dec 10 18:12:05 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from giroc.albury.net.au (giroc.albury.NET.AU [203.15.244.13]) by hub.freebsd.org (Postfix) with ESMTP id 8548637B400 for ; Sun, 10 Dec 2000 18:12:04 -0800 (PST) Received: (from nicks@localhost) by giroc.albury.net.au (8.11.1/8.11.1) id eBB2BwF81483; Mon, 11 Dec 2000 13:11:58 +1100 (EST) Date: Mon, 11 Dec 2000 13:11:58 +1100 From: Nick Slager To: Matt Rudderham Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Putting a Process Into Background Message-ID: <20001211131158.C77951@albury.net.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from matt@researcher.com on Sun, Dec 10, 2000 at 10:01:42PM -0400 X-Homer: Whoohooooooo! Sender: nicks@giroc.albury.net.au Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Matt Rudderham (matt@researcher.com): > I was wondering how to put a process that initially requires some imput, but > then will run on its own into the background to free up the terminal. It's a > setiathome process, as well as another similar one. Basically I'd like > something like ^Z that will give me a shell, but let the process run and not > stop it, preferrably to be able to use fg to bring it back to take a peek at > it. Have a look at screen. It's in the ports collection. Regards, Nick -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message