Re: cron and ssh
From: Stuart J. Browne (stuart_at_promed.com.au)
Date: 07/30/04
- Next message: Chad Lemmen: "Re: cron and ssh"
- Previous message: Greg M Lee: "Re: cron and ssh"
- In reply to: Chad Lemmen: "cron and ssh"
- Next in thread: Chad Lemmen: "Re: cron and ssh"
- Reply: Chad Lemmen: "Re: cron and ssh"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 30 Jul 2004 11:08:42 +1000
"Chad Lemmen" <chad@naboo.lemmen.com> wrote in message
news:GsgOc.42186$qT3.28947@nwrddc03.gnilink.net...
>
> I'm running SCO 5.0.5 and I'm having trouble getting cron to work with
ssh.
> I have openssh 3.4p1 installed and setup so that I can access a Linux box
> without being prompted for a password. Here is the script I'm having
cron
> run
>
> #!/bin/sh
> PATH=/usr/local/bin:$PATH
> ssh linuxhost cat parseshell/price.prn >> /path_on_sco/price.prn ;
> ssh linuxhost rm parseshell/price.prn
>
>
> This script works if I execute it manually, but not if I have cron run
it.
> cron doesn't have a problem with the second ssh line
> 'ssh linuxhost rm parseshell/price.prn' that works with no errors, but
> I'm getting an error with the first ssh line. Cron emails me this
>
> debug1: Sending command: cat parseshell/price.prn
> debug1: channel request 0: exec
> debug1: channel 0: open confirm rwindow 0 rmax 32768
> debug1: channel_free: channel 0: client-session, nchannels 1
> debug1: fd 0 clearing O_NONBLOCK
> debug1: fd 1 clearing O_NONBLOCK
> debug1: fd 2 clearing O_NONBLOCK
> select: Invalid argument
> debug1: Transferred: stdin 0, stdout 0, stderr 26 bytes in 0.0 seconds
> debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 272696336.3
> debug1: Exit status -1
>
> What does 'select: Invalid argument' mean? Is there something wrong with
> my syntax that cron doesn't like? Why does the command work if typed
> at the command line or if the script is run manually, but doesn't
> work with cron?
My thought would be to cut try cutting off STDIN, as it doesn't exist, and
try again:
ssh -n linuxhost "cat parseshell/price.prn" >> /path_on_sco/price.prn
There should also be nothing stopping you combining these two ssh commands
into one either:
ssh -n linuxhost "cat parseshell/price.prn;rm parseshell/price.prn" >>
/path_on_sco/price.prn
Quoting the command string makes for eaiser reading/understanding later as
well.
Give it a shot, see how it goes.
bkx
- Next message: Chad Lemmen: "Re: cron and ssh"
- Previous message: Greg M Lee: "Re: cron and ssh"
- In reply to: Chad Lemmen: "cron and ssh"
- Next in thread: Chad Lemmen: "Re: cron and ssh"
- Reply: Chad Lemmen: "Re: cron and ssh"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|