Can someone shed some light on something for me?

I have a Red Hat 9.0 server I had built here on hot swap disks then
installed on my client's network in his server. The only difference is the
network address. Originally it was configured using IP address
192.168.2.9, now the Ethernet is defined as 192.168.1.7. I don't know how
or if it's pertinent.

I tried to have a cron job copy some files. When the job kicks off it
errors out immediately. Here's the information the root account receives
via e-mail any time I try to run the job:

Subject: Cron <root@forester> * /root/getcorvettersync.sh
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>

/bin/sh: line 1: anaconda-ks.cfg: command not found


Here's the job I'm trying to run:

cat getcorvettersync.sh

#!/bin/bash

RSYNC=/usr/bin/rsync
SSH=/usr/bin/ssh
KEY=/root/foresterkey/forester-rsync-key
RUSER=root
RHOST=192.168.2.8
RPATH=/home/
LPATH=/home/
$RSYNC -tupr -e "$SSH -i $KEY" --verbose --progress --delete $RUSER@$RHOST
$RPATH $LPATH

Well, I'm still searching for a solution. Since the original post I tried logging in as a non-privileged user and submitted a cron job to that user's crontab. There was NO error produced, so it seems like this anaconda-ks.cfg thing is specific to the root account.

Okay I said, I'll just generate ssh keys as the non privileged user and copy files that way, WRONG. Although I could generate the keys and modify my script my account did not have write privileges to /home so I could not create the user directories and files under /home. I made the non-privileged account a member of the root group and chmod -R 774 /home but still no joy. I finally chown -R non-privilegeduser.root /home and I'm able to create directories / files under /home. Problem is that the users now don't have access to their data on the backup server.

I'd really like to have the anaconda-ks.cfg error corrected so root's crontab can execute the rsync job to back up the files.

I have seen two posts on Google with the same exact problem but no resolution.

Help please!

I encountered the same problem today and came across your post while looking for answers. I found this solution on the The Milwaukee Linux User Group mailing list.

http://www.milwaukeelug.org/pipermai...er/001969.html

Anyway I've seen some of this funky stuff happening
when you have too many '*'s in your crontab. If you have

00 12 * * * /command

it will work fine. If you have

00 12 * * * * /command
It will try to execute everything in your home directory.
And I bet that anaconda-ks.cfg is your first file and it
crapped out on that one.

So make sure you don't have too many '*'s"

Hope this helps!

Thanks for your follow-up.

Mea culpa, mea culpa.

I had discovered the extra asterisk but failed to post my findings here. I had also posted the problemon alt.linux.redhat and HAD remembered to post my solution there.

Too many news groups, too little time.

Thanks again.