in reply to perl script and cron

snyder ... this is just like your last post (tar help). I'm just guessing that your IO::Dir is failing since you use a relative path here instead of the absolute path you used before. Before you create the tar file, add some debug statements to see if you actually have any data in your @files array.

-derby

Replies are listed 'Best First'.
Re^2: perl script and cron
by snyder (Initiate) on Mar 23, 2006 at 21:27 UTC
    well, looks like adding the full path to the directory worked. After some thought and derby's post, I concluded the script, running as a cron job is no longer running from within the parent directory therefore the full path is requireed. Thanks derby.
Re^2: perl script and cron
by snyder (Initiate) on Mar 23, 2006 at 21:12 UTC
    derby, with all due respect the post is not the same. I now have a working script. For some reason when cron runs it (as root) it FTP's a tarball to the remote server with the proper name. The problem is the the tar did not complete before the FTP portion of the script was executed. The file that is FTP'd is 1k and should be 60megs. If I run it from command line, it runs fine. The tarball is 60 megs and it show up on the remote server as such. The path to the directory is not an issue as I am running the script from the parent directory.
      The path to the directory is not an issue as I am running the script from the parent directory.

      Yes, from the console but not from cron. When you run a program with cron you should safely assume that the current working directory is pretty much arbitrary. Therefore you need to either use an absolute path when checking the directory or explicitly set the current directory using chdir.