The command does not work, because you need to redirect STDxxx file
handles to /dev/null (or some file(s)) first. You may also need to run a
script interpreter first, or create a separate script in order to be
able to redirect STDxxx handles.
- Alexey.
Dave Bartmess wrote:
I'm trying to do a fo
Rather than trying to get the task to return
quickly, what about trying the task to
invoke the four 's calls at once.
Just my 2 cents,
Ninju
--- Dave Bartmess <[EMAIL PROTECTED]> wrote:
> I'm trying to do a four-task parallel call, using
> sshexec to call the
> remote builds. Each build is a re
I'm trying to do a four-task parallel call, using sshexec to call the
remote builds. Each build is a replica of the calling build, just on a
different platform.
The build script portion is below.
The problem is, when ant executes the sshexec task, despite what I put
in the remotebuild.sh, such a
From: <[EMAIL PROTECTED]>
To: "Ant Users List" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, December 09, 2004 7:02 PM
Subject: Re: Sshexec and nohup
> Maybe it's creating it in a different directory. The file should be in
> the working dire
Sent: Thursday, December 09, 2004 4:03 PM
To: Ant Users List
Cc: [EMAIL PROTECTED]
Subject: Re: Sshexec and nohup
Maybe it's creating it in a different directory. The file should be in
the working directory which may not be the same as the script dir.
Did you try ssh-ing from another box and
:50 PM
Please respond to "Ant Users List"
To: <[EMAIL PROTECTED]>
cc:
Subject:Sshexec and nohup
We have a script(for example start.sh) which has a nohup ./start &
in it, therefore it creates a nohup.out file. When I execute the
start.
We have a script(for example start.sh) which has a nohup ./start &
in it, therefore it creates a nohup.out file. When I execute the
start.sh on the system it creates the nohup.out file and everything is
fine.
I have an ANT build file on a remote system which uses the sshexec task
to execute t
