SMSLink FAQ===========(last modified on 09/12/99)1./ Run-time error after upgrading to 2.2.x kernel    ----------------------------------------------    After upgrading an existing server install to version 2.2.x of the     Linux kernel, you might encounter the following error:    ----------cut-----------    got </dev/gsm>, now sending...    tty_io.c: process 160 (sms_serv) used obsolete /dev/cua0 - update software    to use /dev/ttyS0    ----------cut-----------    To solve this error, go to /dev, remove your gsm softlink to cuax and    create a new one (with the same name) to ttySx (where x is also the    same, obviously). As long as you kept the same name for the gsm    softlink, there's nothing to change in the configuration files.2./ Server hanging in the beginning of the sending process    ------------------------------------------------------        After installing the server software, you want to test it through the    interactive interface (telnet localhost sms), you supply a username,    a destination GSM number and a message, and you then type send. The    server answers:        ----------cut-----------    got </dev/gsm>, now sending...    ----------cut-----------        ...and then hangs.        What is most likely happening is that the directory where the "libmodem"    library would like to store its lock file doesn't exist. By default,     libmodem expects a directory called /usr/spool/uucp. It should be owned     uucp:uucp (or root:root if the uucp user doesn't exist on your system),     and mode drwxrwxrwt (watch for the 't' bit). It is indeed not created by    default on all distributions and / or configurations. Just create it    with the aforementionned rights and ownership if not present. You can    also edit dial/modems.h.in in the libmodem source tree and alter the    LOCKDIR define (not the recommended solution).3./ Server hanging in the beginning of the sending process (bis)    ------------------------------------------------------------        The symptoms here are similar to the previous case. When you type "send",    the server answers:        ----------cut-----------    got </dev/gsm>, now sending...    ----------cut-----------        ...and then hangs.        In the syslog log file, you'll find an entry saying something like:        ----------cut-----------    ...sms_serv[1147]: call to blopen_mdm_line() failed.    ----------cut-----------    What could be happening is that the flow control to the GSM module is    no set correctly. Please check the last field of the relevant line in    /etc/modems. A value of 0 (zero) means hardware flow control. This seems    to work fine with Falcom A1 and Wavecom WMO1. If you have problems with a    Falcom A2, you might want to try with a value of 1 (one). This will use    software flow control (XON-XOFF).        Thanks to Piero Baudino <piero@aries.it> for pointing that out.