[prev in list] [next in list] [prev in thread] [next in thread] 

List:       festival-talk
Subject:    Re: FT: Festival and Cron job (Solved)
From:       Victor Munoz <vmunoz () macul ! ciencias ! uchile ! cl>
Date:       2003-04-02 13:34:00
[Download RAW message or body]

message from Victor Munoz <vmunoz@macul.ciencias.uchile.cl> to festival-talk
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =



> > When cron jobs run they are typically run in a somewhat unusual 
> > environment, most importnatly they probably don't have the path you'd
> > expect.  So I think the about cron job might for two reasons.
> > 
> > One festival isn't in the path, so change your bash script
> > to give an explicit full path to festival.
> > 

>   Thanks for your reply. I thought something like that could be happening,
> so I did try with full paths. As I understand it, the PATH environment
> variable is set to /usr/bin:/bin, and festival is at /usr/bin, HOME is set
> to what it is, and the text.txt I put in the example of my original name
> was in fact $HOME/festival/text.txt, so cron could find it. So I think
> everything was OK, but I'll give another set of trials to check again. 
> 

   I just wanted to let you know that this is solved now. It was a path
problem indeed. Not in the crontab file itself, which had explicit paths,
but in the script that was called by cron. The script had relative paths,
and commands could not be executed. Now I have full paths everywhere, and
it works nicely. Thanks,

							Victor


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
			       Sent Via festival-talk@cstr.ed.ac.uk
		        To unsubscribe mail majordomo@cstr.ed.ac.uk
[prev in list] [next in list] [prev in thread] [next in thread]