Thanks Mike for the reply.  Yes, actually here is the script itself:

#!/bin/sh
tar -zpcvf /home/u1back/u1.hourly.tgz \
  /var/spool/imap \
  /var/imap \
  /var/spool/mqueue

cd /home/u1back
ftp -n -v ntsrv1.emp-reg1.com <<EOF
user <username> <password>
cd /backups/u1
bin
put u1.hourly.tgz
quit

Like I said, this was working fine until yesterday.  The script runs fine
and terminates properly when invoked manully.

--Moby


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mike Burger
Sent: Tuesday, February 20, 2001 09:40 AM
To: [EMAIL PROTECTED]
Subject: Re: New cron


Do you have the command "quit" at the end of your ftp script?

On Tue, 20 Feb 2001, Moby wrote:

> I have a script that tars important files on my RH box and FTPs the
tarball
> over to another machine for backup purposes.  I had a symbolic link to
this
> script in /etc/cron.hourly.  The script ran fine for more than a year.
>
> Yesterday I updates to the latest cron via the binary RPM
> vixie-cron-3.0.1-61 and now my backup script does seem to run.  I found
out
> that the script runs fine when invokes manually.  Trouble-shooting
further,
> I  found that when I run run-parts /etc/cron.hourly, my script kicks off,
> tar everything, FTPs it fine, but never seems to exit from the FTP.  I do
> not think that the new cron RPM touched run-parts, yet all of a sudden the
> script is not working when called from run-parts.  I cannot find a man
page
> for run-parts.  Does anyone have an explanation/resolution for this
problem?
>
> Thanks in advance for your help,
> --Moby
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to