crontab works now!

[Joe-Cho]

Thank you all for responding my questions.
It was my mistake that I didn't pay attention close about the library that I
put
on the files.
I specified the files inside as a relative path, instead  of absolute path.
That's  why I had a problem and they display weird messages.

Anyway, it works now.

One thing, I mention about crontab if you allow.

I guess Jonathan and Kevin both are right.
but, it is a personal preference.

I had to dig what the syntax look like for crontab in my book.
this crontab could be  located anywhere, so that you could register the file
later.

Thank you so much,

Joe Cho
joecho at everestkc.net
a member of kclug.

-----Original Message-----
From: Jonathan Hutchins [mailto:hutchins at tarcanfel.org]
Sent: Thursday, February 13, 2003 3:32 PM
To: joecho at everestkc.net
Cc: dustind at moon-lite.com; kclug at kclug.org
Subject: Re: Output from "cron" command

Quoting Joe-Cho <joecho at everestkc.net>:

> I've gotten this errro message to root every time I execute this
> crontab.
> It seems like it has a perl library problem.

I wonder why you're using perl for this, when all you're doing is
executing a bash command.  I suspect that using quote marks would fix
the problem of putting the command directly in the crontab, but so
would making an executable bash script.

Which user's crontab are you using?  This may be an issue if your
script is not executable by the user who's crontab is running.  This
may also make a difference in the path that perl is searching.

(This is why I do all system work as root, not as a user.)

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/