You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Slavi Pantaleev c0308307e2 Make homeserver services sleep after startup, instead of all dependencies sleeping separately ... This is an attempt at optimizing service startup. The effect is most pronounced when many services are restarted one by one. The systemd service manager role sometimes does this - for example when `just install-service synapse` runs. In such cases, a 5-second delay for each Synapse worker service (or other bridge/bot service that waits on the homeserver) quickly adds up to a lot. When services are all stopped fully and then started, the effect is not so pronounced, because `matrix-synapse.service` starts first and pulls all worker services (defined as `Wants=` for it). Later on, when the systemd service manager role "starts" these worker services, they're started already. Even if they had a 5-second wait each, it would have happened in parallel.		5 months ago
..
defaults	Move matrix-sms-bridge to its own container network and add support for non-Synapse homeservers	5 months ago
tasks	Move matrix-sms-bridge to its own container network and add support for non-Synapse homeservers	5 months ago
templates/systemd	Make homeserver services sleep after startup, instead of all dependencies sleeping separately	5 months ago