The main program of the SMS Server Tools is smsd. It runs other programs if neccessary. You can start smsd in different ways. Tw examples:
Method 1 :
Start smsd by using the startup script. During installation an example startup script will be copied: /etc/init.d/sms or /sbin/init.d/sms. It was tested under SuSE Linux and Solaris. You may need to modify it a little bit for other operating systems.
Run /etc/init.d/sms start to start the SMS Server Tools daemon in background.
Run /etc/init.d/smsd stop to stop the SMS Server Tools daemon.
If you want to run smsd automatically when you boot the computer you need a link to the startup script in the subdirectory init.d/rc3.d or rc2.d. Please read the manual page of init if you don't know how to do this.
Method 2 :
You can run smsd in a terminal windows and (if you like) watch the status monitor that is switched on by the option -s.
Run /usr/local/bin/smsd -s to start the program.
It is a good idea to delete all .LOCK files in the spool directories before you start smsd. You may find old .LOCK files when you stop smsd while it sends or receives messages. It does not delete them automatically.
For example: find /var/spool/sms -name '*.LOCK' -exec rm {} \;
To send a message, put a SMS file in the outgoing queue /var/spool/sms/outgoing and wait a few seconds.
The script /usr/local/bin/sendsms can be used at the command line to create such a file:
sendsms 491721234567 Hello
To read a received message, take a look into the incoming queue /var/spool/sms/incoming.
You should also look into the failed queue /var/spool/sms/failed because it may slowly fill your filesystem up. SMSD puts all messages that failed to send in this queue and leaves them there forever.
If you want to see what command line options are available to smsd, putsms and getsms start them with the option -h:
smsd -h
getsms -h
putsms -h