Difference between revisions of "SMS"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
==Database querying and reporting to SMS== | ==Database querying and reporting to SMS== | ||
*I created php file that queryies database and writes information to a small text file. | *I created php file that queryies database and writes information to a small text file. | ||
| − | *Entry is added to crontab that calls this php file regulary and so keeps information up to date | + | *Entry is added to crontab that calls this php file regulary and so keeps information up to date (at the end of entry I had to add '> /dev/null', not to clutter root email spool with reports |
| − | |||
*Another entry in crontab calls a script that parses new messages in /var/spool/sms/outgoing, does actions triggered by messages and renames / moves these messages | *Another entry in crontab calls a script that parses new messages in /var/spool/sms/outgoing, does actions triggered by messages and renames / moves these messages | ||
Revision as of 13:28, 29 June 2006
SMSserver - instalation and use
Installation and configuration are described on the download site.
- Configuration page suggests that you use syntax 'inbox=directory' while default configuration file installed (/etc/smsd.conf) suggests (and works with !!!) usage 'incoming=yes', where it uses /var/spool/sms/incoming directory as default (created during installation)
Database connectivity (linux to MSSQL)
Database querying and reporting to SMS
- I created php file that queryies database and writes information to a small text file.
- Entry is added to crontab that calls this php file regulary and so keeps information up to date (at the end of entry I had to add '> /dev/null', not to clutter root email spool with reports
- Another entry in crontab calls a script that parses new messages in /var/spool/sms/outgoing, does actions triggered by messages and renames / moves these messages
