Sorry, I missed the first message in this thread. I use rsync with cron
and ssh, but of course with cron you're not there to enter a passphrase or
password. So you have to use security keys and an empty
passphrase. "Eee gads, security is awful" you say, but you can protect
the ssh so that it will only execute the rsync. In the first instance,
generate keys without a passphrase and test it, then work on the security.
You set the allowed command in your authorized_keys file. In my case,
I use a wrapper command that checks the command that ssh wants to
execute, and if it matches some conditions, away we go.
On Fri, 6 Jul 2001, Slattery,Rafe wrote:
> > > You have no controlling terminal.Can't initialize readline for
> > > confirmations.
> > > +++
> > >
> > > command I am using
> > > rsync -e ssh --rsync-path=/export/home/inprise/bin/rsync grainne/*
> > > [EMAIL PROTECTED]:/tmp/gr/
> > >
> > > running on Solaris 2.6, ssh 2.3 and rsync 2.4.1
> >
> > What happens if you use -e 'ssh -n' to tell ssh not to use a tty at
> > all?
>
> nothing..
> session hangs until a ^C or otherise interrupted...(or killed if run via
> cron)
>
> will try updating RSYNC on Monday (once unix admin is back in) and give that
> a go.
>
> just out of curiosity... does anyone else have this combination running
> successfully?
>
> thanks
>
> rafe
>
>
--
Robert Scholten Tel: +61 3 8344 5457 Mob: 0412 834 196
School of Physics Fax: +61 3 9347 4783
University of Melbourne email: [EMAIL PROTECTED]
Victoria 3010 AUSTRALIA http://www.ph.unimelb.edu.au/~scholten
