Carbonio Systemd Targets

To facilitate modular deployment and management, Carbonio introduces four dedicated systemd targets that group services by host role. Each target defines a set of related .service units and manages them as a logical group:

Target Name	Services Included
carbonio-directory-server.target	carbonio-configd, carbonio-stats, carbonio-openldap
carbonio-appserver.target	carbonio-configd, carbonio-stats, carbonio-appserver-db, carbonio-appserver
carbonio-proxy.target	carbonio-configd, carbonio-stats, carbonio-memcached, carbonio-nginx
carbonio-mta.target	carbonio-configd, carbonio-stats, carbonio-postfix, carbonio-opendkim, carbonio-antivirus, carbonio-altermime-config, carbonio-freshclam, carbonio-mailthreat, carbonio-saslauthd.service, carbonio-milter.service

Two key units (carbonio-configd.service and carbonio-stats.service) are shared across all targets and play foundational roles in configuration generation and monitoring.

Systemd vs. zmcontrol

Systemd and the legacy zmcontrol domain are mutually exclusive: you cannot use both at the same time.

If any systemd target is enabled, attempting to run zmcontrol or any legacy control script will produce a warning message.

Warning

Similarly, attempting to start a service with systemctl on Ubuntu 22.04 or Red Hat 8 infrastructure (thus with the services still managed by zmcontrol) will lead to failed startup of services and possible damage done to the infrastructure.

Technical Highlights

• carbonio-configd.service is a prerequisite for most services; it must be up to provide generated configuration.

• All services wait for the unit carbonio-configd.service before starting.

• The only exception is carbonio-openldap.service, which can start independently.

• LDAP availability is checked before carbonio-configd.service activates.

• Only carbonio-directory-server.target can safely start without carbonio-configd.