To make vTigerCRM working with my Asterisk PBX I start a php script (AsteriskClient.php):

root@MSI:~$ cd /var/www/vtigercrm/cron/modules/PBXManager/
root@MSI: /var/www/vtigercrm/cron/modules/PBXManager$ ./AsteriskClient.php

Above script is OK.
(This script must be kept running.....)
So I leave a terminal window open for the script to run

Questions:
1. Why can't I do this with one command?
root@MSI:~$ /var/www/vtigercrm/cron/modules/PBXManager/AsteriskClient.php


2. It looks like this script can't run in the background with &.
Why not?

root@MSI:/var/www/vtigercrm/cron/modules/PBXManager$ ./AsteriskClient.php &


3. To do this automatic 'at boot' I made a crontab :


root@MSI:/var/www/vtigercrm/cron/modules/PBXManager# crontab -l
@reboot cd /var/www/vtigercrm/cron/modules/PBXManager/
@reboot ./AsteriskClient.php

This doesn't seem to work either, because the php script doesn't start. (or starts and stops at once?)

hi,

for starters, the @reboot lines need to be in one line. each line is executed in a seperate process so the "cd" will be in the context of the first process and the ./Asterix.php will be in another context. so when the second line is run it will not be run in the directory that you are expecting.

if you want to do it in this way, add both lines to a bash script and only add that one script to the crontab

i.e.
@reboot /root/startasterix.sh

but, this line should work
root@MSI:~$ /var/www/vtigercrm/cron/modules/PBXManager/AsteriskClient.php
my guess is that from the perspective of the cron process either the php binary is not visible or your php file is missing the #! shell interpreter line (or both)

try something like this on the first line of your php file
#!/usr/local/bin/php -q
of course update the path to match that of your php installation.

1 members found this post helpful.

By default cron has a minimal PATH setting, so it's recommended to always specify absolute/full paths to all cmds & files referenced.
Also, it does not default to the user's home dir, so don't use './blah'.
As said above, put the cmds in a script, full paths and (if reqd) set the reqd PATH in the script.

1 members found this post helpful.

@kubaPL & chrism01:

Thanks for your answers.