fkoch: smsd never deletes them.
Thats a good news. I have already read about the setting incoming_copy but at the moment it is not possible to update to 3.1.16. So first i will take a look at PlaySMS and try to disable it.
Thank you for the quick reply!
|
fkoch: Operating system name and version: Debian 7.3 linux-voyage
Version of smsd: 3.1.5
Smsd installed from: preinstalled on FoxboxGT
Name and model of a modem / phone: Novatel Wireless Expedite EU850D/EU860D/EU870D
Interface: USB
Hello,
i have a problem witch the eventhandler:
after receiving a message, the eventhandlerGSM2 is called and starts a custom script witch the following command ($2 is the filename of the sms):
eventhandlerGSM2:
/path/to/script/myscript $2
This script makes a copy of the message from the spool directory /var/spool/sms/incoming/GSM2.xxxxxx to another folder with following command:
cp $1 /tmp/
This runs well but sometimes (about 1 of 10 messages) the script gives an error and the message could not be copied. This is the output from the smsd.log:
GSM2: SMS receieved, From: xxxxxxxxxxxxx
GSM2: Wrote an incoming message file: /var/spool/sms/incoming/GSM2.xxxxxx
GSM2: Running eventhandler: /etc/sms/scripts/sms/eventhandlerGSM2 RECEIVED /var/spool/sms/incoming/GSM2.xxxxxx
GSM2: Done: eventhandler, execution time 0 sec., status: 0 (0)
GSM2: Exec: eventhandler encountered errors:
GSM2: ! cp: cannot stat `/var/spool/sms/incoming/GSM2.xxxxxx': No such file or directory
It seems that the smsd removes the message before the eventhandler has finished. If i insert a sleep 3 into the eventhandler before the custom script will be executed, every message produces this error:
sleep 3
/path/to/script/myscript $2
How can i be sure that every message will be processed correctly? Does the smsd wait for the eventhandler?
best regards,
Frank
|
