In article <0001HW.C451A8DA002756D5B01AD9AF@[EMAIL PROTECTED]
>,
TaliesinSoft <taliesinsoft@[EMAIL PROTECTED]
> wrote:
>On Wed, 14 May 2008 08:32:44 -0500, TaliesinSoft wrote (in article
><0001HW.C450542C0080D898B01AD9AF@[EMAIL PROTECTED]
>):
>
>[a question as to how one could determine whether cron actually attempted
to
>run an entry in the crontab]
>
>First of all I'm trying (and as I've stated, I'm definitely not versed in
>Unix) to fully understand the suggestions offered in the thread,
suggestions
>which I fully appreciate.
>
>Here is the current contents of my crontab....
>
>====================
>
>0 4 * * * open
>file:///Users/adventures/Library/Application\%20Sup****t/SuperDuper\%21/Schedu
>led\%20Copies/Smart\%20Update\%20SuperDuper\%21\%20from\%20Cowboy.sdsp/Copy\%
>20Job.app
>
>0 5 * * * open
>file:///Users/adventures/Library/Application\%20Sup****t/SuperDuper\%21/Schedu
>led\%20Copies/Smart\%20Update\%20Lefty\%20from\%20Cowboy.sdsp/Copy\%20Job.app
>
>====================
>
>[Some extra blank lines were inserted by Hogwasher in the above]
>
>I don't think it would make any difference but the two "commands" above
are
>preceded by a great many empty lines in the crontab.
>
>
>So, what I am trying to do is in the simplest possible way to determine
>whether cron itself actually ran and responded t
>
>--
Empty lines are ignored, but you have urls rather than directory
locations in this example.
I'm not 100% sure about Leopard cron, but I don't think it
understands url addressing.
Try changing to /Users/you/subdirectory/app (or whereever the app is)
instead of file://....
|
