- Apr 20, 2018
-
-
Erik Johnston authored
-
- Sep 24, 2017
-
-
rnbdsh authored
Starting with synctl lead to "no config file found" Stopping also leads to some (code=exited, status=1/FAILURE), but at least now we can stop the service.
-
rnbdsh authored
Non-existing files, when running the suggested from https://github.com/matrix-org/synapse#configuring-synapse /etc/synapse/log_config.yaml so the --log-config leads to an error /etc/sysconfig/synapse The environment-file or even the /etc/sysconfig does not exist in arch linux Also instead of calling python2 we use synctl, as this seems to be the proper way to start it, and it gives us a more useful error in the systemctl status. And we now allow stop (and therefore restart).
-
- Feb 28, 2017
-
-
Matthew Hodgson authored
merge in right archlinux package, thanks to @saram-kon from https://github.com/matrix-org/synapse/pull/1956
-
- Apr 14, 2016
-
-
Oleg Girko authored
Now there is at least one environment variable that controls synapse server's behaviour: SYNAPSE_CACHE_FACTOR. So, it makes sense to make systemd unit file to use environment configuration file that can set this variable's value. Signed-off-by:
Oleg Girko <ol@infoserver.lv>
-
- May 31, 2015
-
-
Ivan Shapovalov authored
It turned out that merely configuring the root logger is not enough for "catch-all" semantics. The logging subsystem also needs to be told not to disable existing loggers (so that their messages will get propagated to handlers up the logging hierarchy, not just silently discarded). Signed-off-by:
Ivan Shapovalov <intelfx100@gmail.com>
-
- Apr 29, 2015
-
-
Matthew Hodgson authored
-
Ivan Shapovalov authored
The added logger configuration (--log-config or log_config:) uses systemd's python bindings to pass messages directly to the journal. Signed-off-by:
Ivan Shapovalov <intelfx100@gmail.com>
-