(This post is coming from a former athlete)
Sometimes watching (reading) how you all do your magic on this list,
I think of the things Wayne Gretzky and Michael Jordan used to do.
Keep it up debian-users. Good stuff. We are all watching you!!!
Andy
(watching, reading, and learning Debian)
-
-- Michael Kahle <[EMAIL PROTECTED]> wrote
(on Wednesday, 29 January 2003, 02:18 PM -0600):
>
> > From: sean finney wrote:
> > heya,
> >
> > i'd suggest either nohup or screen. the former is dirt
> > simple but not very featureful, and the second is the opposite.
>
> OK, I just installed scree
Michael,
If you start screen, then start your application, you can detach the
screen session while leaving your application running and then later,
reattach to the same screen session from home. You're app will still
be running and you'll be able to see the output. Another solution
mig
> Screen acts as its own virtual terminal. You start screen from any
> terminal and it leaves you at a terminal prompt. Now you can
> do whatever
> you want (i.e. start your backup). From another terminal (ssh'd in or
> otherwise) you can cause that screen virtual terminal to be
> displayed on
On Wed, Jan 29, 2003 at 10:48:04AM -0600, Michael Kahle wrote:
[snip]
> current ssh session? Is there a program that exists to allow me to
> redirect
> the output of a program running in a terminal to another terminal?
> I hope I
> am explaining this clearly.
Michael -
Take a look at the 'screen
Michael Kahle wrote:
I am not sure how to ask for what I want here. But, here goes. I was using
dump to make a backup of a directory on my computer. This was started from
a terminal in X. As it was running I could see in the terminal window all
the status output from the program. Good. This
> From: sean finney wrote:
> heya,
>
> i'd suggest either nohup or screen. the former is dirt
> simple but not very featureful, and the second is the opposite.
OK, I just installed screen, very cool program, but not what I am looking
for. I need to be able to run a program in a window. Then
On Wed, Jan 29, 2003 at 10:48:04AM -0600, Michael Kahle wrote:
> to complete and so I went home while the backup was still running. When at
> home I ssh'd into the box to see if the dump process was still running, it
> was. Then I got to thinking, how can I see the output of this program in my
>
heya,
i'd suggest either nohup or screen. the former is dirt simple but
not very featureful, and the second is the opposite.
hth
sean
On Wed, Jan 29, 2003 at 10:48:04AM -0600, Michael Kahle wrote:
> I am not sure how to ask for what I want here. But, here goes. I was using
> dump to
On Wednesday 29 January 2003 10:48 am, Michael Kahle wrote:
> I am not sure how to ask for what I want here. But, here goes. I was
> using dump to make a backup of a directory on my computer. This was
> started from a terminal in X. As it was running I could see in the
> terminal window all the
-- Michael Kahle <[EMAIL PROTECTED]> wrote
(on Wednesday, 29 January 2003, 10:48 AM -0600):
> I am not sure how to ask for what I want here. But, here goes. I was using
> dump to make a backup of a directory on my computer. This was started from
> a terminal in X. As it was running I could see
Michael Kahle wrote:
> a terminal in X. As it was running I could see in the terminal window all
> the status output from the program. Good. This backup job took a long time
> to complete and so I went home while the backup was still running. When at
> home I ssh'd into the box to see if the du
I am not sure how to ask for what I want here. But, here goes. I was using
dump to make a backup of a directory on my computer. This was started from
a terminal in X. As it was running I could see in the terminal window all
the status output from the program. Good. This backup job took a long
13 matches
Mail list logo