Greg Norris wrote:
Roberto C. Sanchez wrote:
I occasionally log into a machine remotely and start a process in the
background:
command
However, when I log out of the machine, the ssh process on my local
machine blocks.
This is often caused because the process still has a file
On Thu, Sep 01, 2005 at 10:17:33PM -0400, Roberto C. Sanchez wrote:
OK. I should have been more precise in my explanation then. I am
redirecting like this:
command log.txt 21
Is that causing it then?
Possibly. Try redirecting stdin to /dev/null as well... that frequently
takes care
I occasionally log into a machine remotely and start a process in the
background:
command
However, when I log out of the machine, the ssh process on my local
machine blocks. I guess that it is becuase the remote still has jobs
running. Is there a way to get it start the process in the
On Thu, 01 Sep 2005 17:33:28 EDT, Roberto C. Sanchez writes:
command
However, when I log out of the machine, the ssh process on my local
machine blocks.
If you don't care as much about your ssh session as the command running
on, `man nohup`.
cheers,
rw
--
-- Having a firewall that allows
On Thu, Sep 01, 2005 at 11:38:50PM +0200, Robert Waldner wrote:
On Thu, 01 Sep 2005 17:33:28 EDT, Roberto C. Sanchez writes:
command
However, when I log out of the machine, the ssh process on my local
machine blocks.
If you don't care as much about your ssh session as the command
You could do this:
nohup $command
But I always usea trick I find works with bash, so when your in a
bash shell do this:
#start another bash shell
bash
#start your background job
command
#exit the subshell
exit
#exit your ssh connection
exit
That should work.
- D
On 1 Sep 2005 at 17:33,
On Thu, Sep 01, 2005 at 02:52:18PM -0700, [EMAIL PROTECTED] wrote:
You could do this:
nohup $command
But I always usea trick I find works with bash, so when your in a
bash shell do this:
#start another bash shell
bash
#start your background job
command
#exit the subshell
exit
On Thu, 01 Sep 2005 17:44:46 EDT, Roberto C. Sanchez writes:
If you don't care as much about your ssh session as the command running
on, `man nohup`.
That wasn't it. I still had to kill the ssh process on my local
machine after starting the remote process.
Of course that wasn't it. The
Do you want to use `at' ?
Roberto C. Sanchez wrote:
On Thu, Sep 01, 2005 at 02:52:18PM -0700, [EMAIL PROTECTED] wrote:
You could do this:
nohup $command
But I always usea trick I find works with bash, so when your in a
bash shell do this:
#start another bash shell
bash
#start your
* Roberto C. Sanchez [EMAIL PROTECTED] [2005-09-01 16:45]:
Is there a way to get it start the process in the background
and then detach from the shell?
I use screen for these sorts of things
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
On 9/1/05, Roberto C. Sanchez [EMAIL PROTECTED] wrote:
However, when I log out of the machine, the ssh process on my local
machine blocks. I guess that it is becuase the remote still has jobs
running. Is there a way to get it start the process in the background
and then detach from the
On Fri, Sep 02, 2005 at 12:20:10AM +0200, Robert Waldner wrote:
On Thu, 01 Sep 2005 17:44:46 EDT, Roberto C. Sanchez writes:
If you don't care as much about your ssh session as the command running
on, `man nohup`.
That wasn't it. I still had to kill the ssh process on my local
On Thu, Sep 01, 2005 at 03:38:35PM -0700, David Kirchner wrote:
On 9/1/05, Roberto C. Sanchez [EMAIL PROTECTED] wrote:
However, when I log out of the machine, the ssh process on my local
machine blocks. I guess that it is becuase the remote still has jobs
running. Is there a way to get it
On Thu, Sep 01, 2005 at 11:10:19PM +0100, Jerome BENOIT wrote:
Do you want to use `at' ?
That seems a bit kludgy. I suppose I could always do `at now + 1 min`
or something like that.
-Roberto
--
Roberto C. Sanchez
http://familiasanchez.net/~roberto
pgpTv4cQaT113.pgp
Description: PGP
Roberto C. Sanchez wrote:
On Thu, Sep 01, 2005 at 11:10:19PM +0100, Jerome BENOIT wrote:
Do you want to use `at' ?
That seems a bit kludgy. I suppose I could always do `at now + 1 min`
or something like that.
-Roberto
at -f SCRIPT now
see `man at' for further informations
I do
On Fri, Sep 02, 2005 at 12:18:50AM +0100, Jerome BENOIT wrote:
Roberto C. Sanchez wrote:
On Thu, Sep 01, 2005 at 11:10:19PM +0100, Jerome BENOIT wrote:
Do you want to use `at' ?
That seems a bit kludgy. I suppose I could always do `at now + 1 min`
or something like that.
-Roberto
at
On Thu, Sep 01, 2005 at 05:33:28PM -0400, Roberto C. Sanchez wrote:
I occasionally log into a machine remotely and start a process in the
background:
command
However, when I log out of the machine, the ssh process on my local
machine blocks. I guess that it is becuase the remote still
On Thu, Sep 01, 2005 at 09:09:54PM -0500, Greg Norris wrote:
On Thu, Sep 01, 2005 at 05:33:28PM -0400, Roberto C. Sanchez wrote:
I occasionally log into a machine remotely and start a process in the
background:
command
However, when I log out of the machine, the ssh process on my
Yes, screen is a good choice.
- Original Message -
From: Paul Stolp [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Cc: Roberto C. Sanchez [EMAIL PROTECTED]
Sent: Friday, September 02, 2005 6:20 AM
Subject: Re: Starting background process in ssh session
* Roberto C. Sanchez [EMAIL
19 matches
Mail list logo
