Problem solved. There _is_ a syntax error.
On Thu, 2004-04-29 at 08:57, Howard Lowndes wrote: > I had a bash script that contains a lot of rsync commands and works fine > as a straight forward script. > > During restructuring of this script I put the rsync commands into a > series of bash function statements and then call the required function > from a case/esac conditional. > > Syntactically there is no problem but the weird thing is that the rsync > commands won't run and the complaint is that they cannot find rsh (I > have set -x in there to see what is happening): > backup:~# /usr/local/sbin/rsync.sh > ++ date +%H > + sync_grp_c > + rsync -aq --delete aufint:aufintmates /mnt/backup/aufintmates > Failed to exec rsh : No such file or directory > rsync error: error in IPC code (code 14) at util.c(162) > rsync: connection unexpectedly closed (0 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(150) > + rsync -aq --delete aufint:aufintpgsql /mnt/backup/aufintpgsql > Failed to exec rsh : No such file or directory > rsync error: error in IPC code (code 14) at util.c(162) > rsync: connection unexpectedly closed (0 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(150) > + sync_grp_h > + : > > > > Any clues as to why rsync would suddenly be wanting to run rsh? -- Howard. LANNet Computing Associates - Your Linux people <http://www.lannetlinux.com> ------------------------------------------ Flatter government, not fatter government - Get rid of the Australian states. ------------------------------------------ To mess up a Linux box, you need to work at it; to mess up your Windows box, you just need to work on it. - Scott Granneman, SecurityFocus -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
