The cron job definition has been fine all along; the bash script fires fine as well, but the referenced line , below, in the script that runs the basexclient does not seem to be running.

 

On Mon, Feb 11, 2013 at 7:56 AM, Jens Erat <jens.erat@uni-konstanz.de> wrote:
Has the misspelled path been in your crontab or only your mail? Is it working now?

You didn't reply on this line:

> - Which user's crontab is that line in, the user's you've been testing the script from?


--
Jens Erat

 [phone]: tel:+49-151-56961126
  [mail]: mailto:email@jenserat.de
[jabber]: xmpp:jabber@jenserat.de
   [web]: http://www.jenserat.de

     PGP: 350E D9B6 9ADC 2DED F5F2  8549 CBC2 613C D745 722B



Am 11.02.2013 um 13:44 schrieb rsr <robt.s.ryan@gmail.com>:

> thanks for the replys
>
> 1 - its ok to stack multiple commands in cron, i do it all the time
> 2 - yes, i miskeyed my cron line is should be  "40 * * * * cd /home/xxx; ./basexjob.sh"
> 3 - line in my bash script is "/home/xxx/basex/bin/basexclient -Uxxx -Pxxx < /home/xxx/load.bxs"
>
>
>
>
>
>
> On 02/11/2013 07:18 AM, Jens Erat wrote:
>> Hi!
>>
>>> 40 * * *  * cd home/xxx; ./basexjob.sh
>> - Which user's crontab is that line in, the user's you've been testing the script from?
>> - `home/xxx` looks weird, do you probably mean `/home/xxx`?
>> - What's inside your `basexjob.sh`?
>>
>> - - -
>>
>> On Andria's comments:
>>
>>> I don't know if you can use sequence of commands on crontab
>> That's fine.
>>
>>> while I would use "/home/xxx/basexjob.sh" instead of "cd home/xxx; ./basexjob.sh"
>> The script could depend on the current path. If it doesn't, I'd prefer that, too.
>>
>> Regards form Lake Constance, Germany,
>> Jens
>>
>
> _______________________________________________
> BaseX-Talk mailing list
> BaseX-Talk@mailman.uni-konstanz.de
> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk