Re: [tlug] Odd cron/crontab result.

["Nguyen Vu Hung" <vuhung16plus@example.com>]

On 9/15/06, burlingk@example.com <burlingk@example.com> wrote:
> > -----Original Message-----
> > From: tlug-bounces@example.com [mailto:tlug-bounces@example.com?? On
> > Behalf Of bruno raoult
> > Sent: Friday, September 15, 2006 8:23 AM
> > To: Tokyo Linux Users Group
> > Subject: Re: [tlug] Odd cron/crontab result.
> <snip>
> > I think the script itself has a pb, not crontab.
> > You could write a one line script, just writing the date
> > in a file somewhere, just to confirm if the problem is
> > coming from your script or from cron itself.
> <snip>
>
> I agree, that is the most likely possability.  cron itself doesn't
> usually enforce limitations on the time as far as I know.  The crontab
> file itself is all the configuration that is generally needed.  Whatever
> it says, is what it should do.
>
> I know, I am basically being repetative.  ^^;;  Like he said, check the
> script. :)

His script is working fine with crontab on Solaris, but it doesn't
work on FDC4 So not only the script has to be checked, FDC4 settings
have to be checked, too.

@example.com: How do you check that the script is running fine every hours? Do
you confrim its operation by looking at system logs or its output?

--
Best Regards,
Nguyen Hung Vu
vuhung16plus{remove}@example.com
VIQR Standard: http://vi.i18n.kde.org/viqr.txt