Also keep in mind that crontab runs under a different environment than
your regular shell.
You may be relying on paths that are present by default on your
regular shell, but not on the crontab.
You can try chrooting to /etc/kannel before calling, or make sure that
all your paths (I mean also on the config files) are absolute
("/etc/kannel/whatever/file" instead of just "whatever/file").
BTW, why are you executing kannel from a crontab? I'd go for a rc.d or
startup script instead.
Last but not least, check the documentation regarding kannel startup options.
Hint: the --parachute switch it's your best friend ;)
Regards,
Alejandro.
On 1/29/07, Juan Nin <[EMAIL PROTECTED]> wrote:
mhmhm
are you sure your path to the executables is "/etc/kannel/bearerbox" and
"/etc/kannel/smsbox"??
was this a typo on your e-mail, or on your script??
or do you really have the executables on /etc/kannel??
Regards,
Juan
wanted wrote:
>hi all,
>I have a shell script which will startup bearerbox and smsbox as follows:
>
>/etc/kannel/bearerbox /etc/kannel/conf/bearerbox.conf &
>/etc/kannel/smsbox /etc/kannel/conf/smsbox.conf &
>
>The script run well when I manually execute the script. However, if the
>script is scheduled in crontab, I noticed that bearerbox and smsbox will not
>be executed even though the script is being executed successfully.
>Nothing is being output to the log file even though the log level is
>configured to 'DEBUG' level. Is there any enviroment parameter need to be
>assign?
>Any suggestion/opinion is welcomed.
>
>Thanks
>
>
>
>
>
>
--
Alejandro Guerrieri
Magicom
http://www.magicom-bcn.net/
LinkedIn: http://www.linkedin.com/in/aguerrieri
