Date: Sat, 2 Jun 2007 14:05:31 +0200 From: Erik Trulsson <ertr1013@student.uu.se> To: Paul Fraser <pfraser@gmail.com> Cc: Jeremy Gransden <jeremy.gransden@gmail.com>, freebsd-questions@freebsd.org Subject: Re: See output of local xterm session on remote ssh session. Message-ID: <20070602120530.GA23984@owl.midgard.homeip.net> In-Reply-To: <f82eafcc0706020444r46edf1aeu9b8be6dd95cfa6b0@mail.gmail.com> References: <87f7f4170706020423x6f67e84bv366cc765d21529a6@mail.gmail.com> <f82eafcc0706020444r46edf1aeu9b8be6dd95cfa6b0@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 02, 2007 at 09:44:58PM +1000, Paul Fraser wrote: > On 6/2/07, Jeremy Gransden <jeremy.gransden@gmail.com> wrote: > >how > >can I then connect to it from my laptop and see the output of that process > >via the ssh session? > > A very popular solution is screen (sysutils/screen). Run a screen > session, then you can share the session from any number of clients, or > attach/detach at will. Quite good if, for example you're running a > process (within a screen session, of course!) in an xterm, and you > want to restart X. Simply detach the screen session, restart X, then > reattach screen to your xterm. But if you already have started the process that you wish to monitor and did not have the foresight to start it in some special manner then neither sysutils/screen, script(1) or redirecting the output to a file will help. Using watch(8) can help though. -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070602120530.GA23984>