Re: Background jobs from ssh
- From: Bit Twister <BitTwister@xxxxxxxxxxxxxxxx>
- Date: Fri, 16 Feb 2007 14:16:54 -0600
On 16 Feb 2007 14:53:11 -0500, Richard E. Silverman wrote:
"BT" == Bit Twister <BitTwister@xxxxxxxxxxxxxxxx> writes:
BT> On 16 Feb 2007 10:42:41 -0800, jhavero@xxxxxxxxx wrote:
>> However, my plink command won't return util the background jobs
>> have finished. I don't want my ssh client to have to wait. Is there
>> any way around this?
BT> man nohup
I don't think this is relevant. This would prevent background jobs from
being killed off in certain circumstances. His problem is that the SSH
session is waiting for the jobs. Perhaps:
Well shucky dern. I would have thought nohuping job1 and job2 would
solve the problem. Should have tested it. :(
This might work instead.
plink user@hostname -pw password "at -f /home/user/start.sh now"
.
- Follow-Ups:
- Re: Background jobs from ssh
- From: Ignoramus2215
- Re: Background jobs from ssh
- References:
- Background jobs from ssh
- From: jhavero
- Re: Background jobs from ssh
- From: Bit Twister
- Re: Background jobs from ssh
- From: Richard E. Silverman
- Background jobs from ssh
- Prev by Date: Re: Background jobs from ssh
- Next by Date: Re: Background jobs from ssh
- Previous by thread: Re: Background jobs from ssh
- Next by thread: Re: Background jobs from ssh
- Index(es):