Can you give an actual example of something that fails?
--
Les Mikesell
Les, it's not that it fails it is just that plink sends the command and waits
for it to complete execution. Even if the shell script uses your nohup syntax,
if I put in a long dd as a test command then have plink
Joseph L. Casale wrote:
Can you give an actual example of something that fails?
--
Les, it's not that it fails it is just that plink sends the command and waits
for it to complete execution. Even if the shell script uses your nohup syntax,
if I put in a long dd as a test command then have
nohup will allow you to run a command that is not connected to the shell:
nohup command nohup.log
Devin,
What is the correct way to encapsulate the command if its rather long. Just as
a test, I am trying to run `dd if=/dev/random of=~/test bs=1024 count=5` so
that I can disconnect and
Joseph L. Casale wrote:
nohup will allow you to run a command that is not connected to the shell:
nohup command nohup.log
Devin,
What is the correct way to encapsulate the command if its rather long. Just as
a test, I am trying to run `dd if=/dev/random of=~/test bs=1024 count=5`
put everything in a shell script, and run the script.
Yea, I tried that but neglected to see how it behaved from inside an ssh
session. It works there but with plink :(
Back to the drawing board...
jlc
___
CentOS mailing list
CentOS@centos.org
put everything in a shell script, and run the script.
Yea, I tried that but neglected to see how it behaved from inside an ssh
session. It works there but with plink :(
Back to the drawing board...
jlc
For those that followed, a working solution came from a helpful soul in an ssh
list
Joseph L. Casale wrote:
put everything in a shell script, and run the script.
Yea, I tried that but neglected to see how it behaved from inside an ssh
session. It works there but with plink :(
Back to the drawing board...
I just tried:
% cat /tmp/test.sh
nohup /usr/bin/tail -f
Joseph L. Casale wrote:
I just tried:
% cat /tmp/test.sh
nohup /usr/bin/tail -f /tmp/test.in /tmp/test.out 21
(note that all output is redirected)
C:\ plink [EMAIL PROTECTED] /tmp/test.sh
...
C:\
on the remote host
% echo 10 /tmp/test.in
% cat /tmp/test.out
...
10
% ps ax|grep tail
...
Try using screen?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Joseph L. Casale
Sent: Monday, March 17, 2008 5:14 PM
To: 'centos@centos.org'
Subject: [CentOS] remote command execution
I need to launch a job remotely from a Windows machine
Joseph L. Casale wrote:
I need to launch a job remotely from a Windows machine on a CentOS box, the
caveat is that I can't maintain a connection once I have initiated the job.
Anyone got an idea how I can accomplish this?
Thanks!
jlc
winscp
http://winscp.net
--
Kari Salovaara
Hanko,
: Mon Mar 17 18:13:48 2008
Subject: [CentOS] remote command execution
I need to launch a job remotely from a Windows machine on a CentOS box, the
caveat is that I can't maintain a connection once I have initiated the job.
Anyone got an idea how I can accomplish this?
Thanks!
jlc
I got the BSD and negate forms mixed up and forgot the .
C:\rsh host stty -hup; command
-Ross
- Original Message -
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: centos@centos.org centos@centos.org
Sent: Mon Mar 17 18:27:58 2008
Subject: Re: [CentOS] remote command execution
Use rsh
I'm wrong! Uh! Take that mister know-it-all.
Check out:
http://www.faqs.org/faqs/unix-faq/faq/part3/section-2.html
(God I've got some issues)
-Ross
Heh, I see the example for sh and I am note to sure exactly what it's doing but
I will give it a try! That looks most promising as Win2k3 has an
I won't allow rsh to contact my CentOS machines. ssh, ssl, http, but no
rsh. Too insecure, especially from a Windows machine.
Ken Wolcott
On Mon, Mar 17, 2008 at 4:24 PM, Joseph L. Casale [EMAIL PROTECTED]
wrote:
I'm wrong! Uh! Take that mister know-it-all.
Check out:
nohup will allow you to run a command that is not connected to the shell:
nohup command nohup.log
On Mon, Mar 17, 2008 at 5:24 PM, Joseph L. Casale
[EMAIL PROTECTED] wrote:
I'm wrong! Uh! Take that mister know-it-all.
Check out:
Kenneth Wolcott wrote:
I won't allow rsh to contact my CentOS machines. ssh, ssl, http, but no
rsh. Too insecure, especially from a Windows machine.
Rsh uses only the source IP for authentication - which might be OK on
well firewalled internal networks but it generally is not used these
Rsh uses only the source IP for authentication - which might be OK on
well firewalled internal networks but it generally is not used these
days. The same concept will work from ssh too, where you can use keys
for passwordless access. Just
ssh host 'nohup command '
On the other hand, if
17 matches
Mail list logo
