Re: See output of local xterm session on remote ssh session.

2007-06-05 Thread Tek Bahadur Limbu

Pieter de Goeje wrote:

On Saturday 02 June 2007, Jeremy Gransden wrote:

Hello,

I have been searching Google for a few days for this but have not been
coming up with the correct answer. Then again maybe I am asking the wrong
question... If I start a process, i.e. compile a kernel, on my desktop, how
can I then connect to it from my laptop and see the output of that process
via the ssh session?

thanks,
Jeremy
screen(1) is the tool for this. You can find it in the ports collection 
(sysutils/screen).


For example:
$ screen
$ cd /usr/src; sudo make buildworld
(now press CTRL+A D)

On the other machine, ssh into the desktop
$ screen -r
(press CTRL+A D if you've seen enough)

Also, this will protect the running job from accidental (or purposefully) 
closure of the terminal.


Wow, always thought of learning how to learn this magic. Thanks for 
sharing this wonderful tip!



Thanking you...

FreeBSD Rocks!



HTH,
Pieter de Goeje
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: See output of local xterm session on remote ssh session.

2007-06-05 Thread youshi10

On Tue, 5 Jun 2007, Tek Bahadur Limbu wrote:


Pieter de Goeje wrote:

On Saturday 02 June 2007, Jeremy Gransden wrote:

Hello,

I have been searching Google for a few days for this but have not been
coming up with the correct answer. Then again maybe I am asking the wrong
question... If I start a process, i.e. compile a kernel, on my desktop, 
how

can I then connect to it from my laptop and see the output of that process
via the ssh session?

thanks,
Jeremy
screen(1) is the tool for this. You can find it in the ports collection 
(sysutils/screen).


For example:
$ screen
$ cd /usr/src; sudo make buildworld
(now press CTRL+A D)

On the other machine, ssh into the desktop
$ screen -r
(press CTRL+A D if you've seen enough)

Also, this will protect the running job from accidental (or purposefully) 
closure of the terminal.


Wow, always thought of learning how to learn this magic. Thanks for sharing 
this wonderful tip!



Thanking you...

FreeBSD Rocks!



HTH,
Pieter de Goeje


Don't forget to run screen -wipe from time to time to get rid of leftover 
screen sockets though. Doesn't happen often, but if screen dies or the machine 
reboots spontaneously, this will happen..
-Garrett

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


See output of local xterm session on remote ssh session.

2007-06-02 Thread Jeremy Gransden

Hello,

I have been searching Google for a few days for this but have not been
coming up with the correct answer. Then again maybe I am asking the wrong
question... If I start a process, i.e. compile a kernel, on my desktop, how
can I then connect to it from my laptop and see the output of that process
via the ssh session?

thanks,
Jeremy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: See output of local xterm session on remote ssh session.

2007-06-02 Thread Roland Smith
On Sat, Jun 02, 2007 at 07:23:45AM -0400, Jeremy Gransden wrote:
  Hello,
 
  I have been searching Google for a few days for this but have not been
  coming up with the correct answer. Then again maybe I am asking the wrong
  question... If I start a process, i.e. compile a kernel, on my desktop, how
  can I then connect to it from my laptop and see the output of that process
  via the ssh session?

The easiest way would be to start the process from your ssh session.

If you want to keep tabs on an already running process, you should start
the process in such a way that it redirects the standard output and
standard error streams to a file. How that's done depends on the shell
you're using. You can then watch that file via ssh with 'tail -f'.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpZaKFVrPNco.pgp
Description: PGP signature


Re: See output of local xterm session on remote ssh session.

2007-06-02 Thread Paul Fraser

On 6/2/07, Jeremy Gransden [EMAIL PROTECTED] 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.

--
Regards,

Paul Fraser
http://furyc0de.net/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: See output of local xterm session on remote ssh session.

2007-06-02 Thread Pieter de Goeje
On Saturday 02 June 2007, Jeremy Gransden wrote:
 Hello,

 I have been searching Google for a few days for this but have not been
 coming up with the correct answer. Then again maybe I am asking the wrong
 question... If I start a process, i.e. compile a kernel, on my desktop, how
 can I then connect to it from my laptop and see the output of that process
 via the ssh session?

 thanks,
 Jeremy
screen(1) is the tool for this. You can find it in the ports collection 
(sysutils/screen).

For example:
$ screen
$ cd /usr/src; sudo make buildworld
(now press CTRL+A D)

On the other machine, ssh into the desktop
$ screen -r
(press CTRL+A D if you've seen enough)

Also, this will protect the running job from accidental (or purposefully) 
closure of the terminal.

HTH,
Pieter de Goeje
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: See output of local xterm session on remote ssh session.

2007-06-02 Thread Thomas Dickey
On Sat, Jun 02, 2007 at 01:39:08PM +0200, Roland Smith wrote:
 If you want to keep tabs on an already running process, you should start
 the process in such a way that it redirects the standard output and
 standard error streams to a file. How that's done depends on the shell
 you're using. You can then watch that file via ssh with 'tail -f'.

'script' is less intrusive (and allows one to capture _everything_ sent
to the terminal - ymmv)

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpkKIN4lZWjq.pgp
Description: PGP signature


Re: See output of local xterm session on remote ssh session.

2007-06-02 Thread Erik Trulsson
On Sat, Jun 02, 2007 at 09:44:58PM +1000, Paul Fraser wrote:
 On 6/2/07, Jeremy Gransden [EMAIL PROTECTED] 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
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]