From owner-freebsd-questions@FreeBSD.ORG Fri Apr 4 08:40:45 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6A0837B401 for ; Fri, 4 Apr 2003 08:40:45 -0800 (PST) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4580843F85 for ; Fri, 4 Apr 2003 08:40:45 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h34GefNv059158; Fri, 4 Apr 2003 10:40:41 -0600 (CST) (envelope-from dan) Date: Fri, 4 Apr 2003 10:40:41 -0600 From: Dan Nelson To: Jeff Shevlen Message-ID: <20030404164040.GT3344@dan.emsphone.com> References: <20030404142919.GA1472@babylon.polands.org> <1049466814.717.0.camel@localhost> <20030404163346.GA87671@pho88.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030404163346.GA87671@pho88.net> X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: questions@freebsd.org cc: Matthew Smith Subject: Re: How to write to console X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Apr 2003 16:40:46 -0000 In the last episode (Apr 04), Jeff Shevlen said: > I hate to add a variation on a thread before it's been solved, but is > it possible to "jump into" a console from an outside process? Lets > say you have a remote machine and you want to check in on a process > underway in ttyv0? Can you do it? (Not urgent, but a coworker and I > were trying to figure this one out yesterday and this thread is too > similar not to ask...) If you have the snp device in the kernel, you can use the 'watch' command to attach to any TTY and get a copy of all output sent to it. You won't be able to read what's already on the screen, though, since ttys themselves don't have a history. One exception is vtys ( /dev/ttyv* ). Syscons consoles do have a history, and you can use the vidcontrol command to display that (see the -P and -H switches). The best solution is to use ports/misc/screen and run your jobs in a screen session that you then attach to remotely later. -- Dan Nelson dnelson@allantgroup.com