SMS Server Tools

Setting up Logging

Normally smsd uses the syslog daemon (or event log on Windows) to create a log file. To get detailed help about syslog look into its manual page.

You can change this behavior to write a log file if you need it. But using syslog is more flexible.

If you want a list of all possible log entries and loglevels go into the src directory and enter grep LOG_ *.c


This document was written to help for a quick start with syslog:

The following was tested on the SuSE 7.0 Linux distribution but it should work on all Unix 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 or /var/adm/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.conf and add this line:

daemon.debug -/var/log/daemon.log

Then you have to restart the syslog daemon by typing "/sbin/init.d/syslog restart" or "/etc/init.d/syslog restart". Now syslog gives you all possible messages from daemons in this file.

You can watch the file in realtime using the command

tail -f /var/log/daemon.log

If you want more filter methods you can replace syslog with Metalog. It offers more flexible configuration and a lot of useful features.