sympa-community.github.io

Incubating the new Sympa documentation site

Automate startup

Systemd

  1. Units should be customized to ensure Sympa starts after database server (if you run it except SQLite on the same host as Sympa). It can be done by creating a configuration file /etc/systemd/system/sympa.service.d/dependencies.conf. Its content is, for example you are using MySQL:
    [Unit]
    Requires=mysql.service
    After=mysql.service
    

    You may replace mysql above with the name of database service you are using: mariadb, postgresql and so on.

    Note that database service should also start before HTTP service.

  2. Some paths may be placed under volatile directory, for example PID directory /run/sympa under /run (usually bound to /var/run). They have to be recreated at the next boot-up time. If it is the case, create /usr/lib/tmpfiles.d/sympa.conf with the content:
    d /run/sympa 0755 sympa sympa -
    

    On binary releases, volatile directories will be managed automatically.

  3. Activate Sympa service.
    # systemctl enable sympa.service
    

You should activate other services also: Mail transfer agent (MTA) and HTTP server.

FreeBSD ports

  1. Activate Sympa service.
    # sysrc sympa_enable=YES
    

You should activate other services also: Database server, mail transfer agent (MTA) and HTTP server.

initscripts

  1. Activate Sympa service.
    # chkconfig sympa on
    

You should activate other services also: Database server, mail transfer agent (MTA) and HTTP server.

CC BY-SA 4.0 Unless otherwise specified, the contents of this document are licensed under the Creative Commons - Attribution - ShareAlike license. For more details see LICENSE and AUTHORS.

Theme originally designed by orderedlist