1. Carta.tech
2. Packages
3. gammu-smsd

• 3

  Section 1: Executable programs or shell commands

  gammu-smsd.1

  Sms daemon for gammu

  gammu-smsd-inject.1

  Inject messages into queue of sms daemon for gammu

  gammu-smsd-monitor.1

  Monitor state of sms daemon for gammu

• 1

  Section 5: File formats and conventions

  gammu-smsdrc.5

  Gammu-smsd(1) configuration file

• 9

  Section 7: Miscellaneous

  gammu-smsd-dbi.7

  Gammu-smsd(1) backend using dbi abstraction layer to use any supported database as a message storage

  gammu-smsd-files.7

  Gammu-smsd(1) backend using filesystem as a message storage

  gammu-smsd-mysql.7

  Gammu-smsd(1) backend using mysql database server as a message storage

  gammu-smsd-null.7

  Gammu-smsd(1) backend not storing messages

  gammu-smsd-odbc.7

  Gammu-smsd(1) backend using odbc abstraction layer to use any supported database as a message storage

  gammu-smsd-pgsql.7

  Gammu-smsd(1) backend using postgresql database server as a message storage

  gammu-smsd-run.7

  Documentation for runonreceive directive

  gammu-smsd-sql.7

  Gammu-smsd(1) backend using sql abstraction layer to use any supported database as a message storage

  gammu-smsd-tables.7

  Description of tables for database backends of gammu-smsd(1) the backends themselves are described in their sections, this document describes general database structure and required tables. more sms daemons can share single database. if you do not specify phoneid in their configuration, all are treated equally and you have no guarantee which one sends outgoing message. if you configure phoneid and use it when inserting message to the outbox table (gammu-smsd-inject does this), each sms daemon will have separate outbox queue.