There are some people who do not know how to use the logging output from
smsd, getsms and putsms. I hope this document wil help a little bit.

The following was tested on the SuSE 7.0 Linux distribution but it should
work on all Linux systems. The pathnames may differ.

Since version 1.0.5 the programs write all output using the syslog daemon.
This means that there is no longer a special log file. The use of syslog
allows remote control of the program and this method is the unix standard
for most daemons.

Syslog is normally configured to write most messages in the file 
/var/log/messages. They do not include debug messages wich are normally not
useful for you.

But if you have trouble with the sms tools the debug messages are very useful
to you and I need them everytime you report a bug or problem. So you have to
configure syslog to give you all messages. This is simple. Just edit 
/etc/syslog.cong and change the line for /var/log/messages to this:

*.* /var/log/messages

Then you have to restart the syslog daemon by typing "/sbin/init.d/syslogd 
restart". Now syslog gives you all possible messages in one file.



Ok, now you may prefer one logfile for the SMS Server Tools that contains no 
messages from other program. You should look into the syslog manual pages 
because they explain the use of named pipes and fifos.

first you have to create a fifo by typing "mkfifo /tmp/smslog". Then you have 
to tell syslogd to write the output of all daemons to this pipe. Smsd, getsms
and putsms tell syslog that they are daemons. Edit /etc/syslog.conf and
insert the following line:

daemon.* |/tmp/smslog

Now restart syslogd by typing "/sbin/init.d/syslog restart". Now you get all
messages from daemons in this pipe. You can read the pipe by typing 
"cat </tmp/smslog". To filter out only the messages of sms programs you have
to use grep instead of cat by typing "grep sms </tmp/smslog".

