ansaurus

Question

Bind application to several Linux terminals

Answer 1

+1 A:

The quick and dirty way to do this is to redirect the child process' output to a (temporary) file.

A terminal tracking that file can then be started using a command like

xterm -e tail -f /tmp/child1.out

This terminal can be closed and opened when needed.

If you'd rather not store the output in a file, you can use a fifo (see mkfifo(1)), but then you lose the ability to see the past output, since a fifo doesn't store data.

Michiel Buddingh' 2009-06-11 08:01:24

I thought about pumping the output into a FIFO the question is if nobody is reading from the FIFO and my application is running for weeks won't it fill the OS's RAM with this needless output?

Jack 2009-06-11 08:15:26

Nope. It will block you program. :-)

Thomas 2009-06-11 08:44:08

Are there any restrictions on how much a process can write into a pipe before the reader will start emptying it?

Jack 2009-06-11 09:00:00

Yes. For your purposes you can't use a FIFO unless you intend to have the reader running all the time. If you are serious about writing for weeks w/o a reader than a regular file (probably with some kind of rotation after reaching a certain size) is the only real choice.

Duck 2009-06-12 04:00:17

Answer 2

A:

from your terminal, run:

touch proc1.log
xterm -e tail -f proc1.log
topuch proc2.log
xterm -e tail -f proc2.log
/run/proc/1.sh >> proc1.log
/run/proc/2.sh >> proc2.log

now you have 2 terminals following the output of the spawned processes

dsm 2009-06-11 08:11:03

Answer 3

A:

Screen can do this. You can start a detached screen with the new program.

Something like:

screen -d -m -S my-emacs-session emacs foo.c

Thomas 2009-06-11 08:31:13

ansaurus

tags:

views:

answers:

Bind application to several Linux terminals

related questions