summary refs log tree commit diff
path: root/contrib/systemd (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Update example systemd service fileErik Johnston2019-07-221-1/+3
|
* Move logging utilities out of the side drawer of util/ and into logging/ (#5606)Amber Brown2019-07-041-1/+1
|
* Set syslog identifiers in systemd units (#5023)Christoph Müller2019-05-101-1/+1
|
* Update the example systemd config to use a virtualenv (#4273)Richard van der Hoff2018-12-072-22/+31
| | | | | If you're installing as a system package, the system package should have set up the systemd config, so it's more useful to give an example of running in a virtualenv here.
* Document contrib directoryErik Johnston2018-04-201-0/+4
|
* Start traditionally, stop synctlrnbdsh2017-09-241-1/+2
| | | | 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.
* Remove non-existing files, add stop, use synctlrnbdsh2017-09-241-2/+2
| | | | | | | 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).
* merge in right archlinux package, thanks to @saram-kon from ↵Matthew Hodgson2017-02-281-1/+1
| | | | https://github.com/matrix-org/synapse/pull/1956
* Add environment file to systemd unit configuration.Oleg Girko2016-04-141-0/+1
| | | | | | | | | 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>
* contrib/systemd: log_config.yaml: do not disable existing loggersIvan Shapovalov2015-05-311-0/+2
| | | | | | | | | 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>
* minimal docMatthew Hodgson2015-04-291-0/+4
|
* contrib/systemd: add a sample systemd unit file and a logger configurationIvan Shapovalov2015-04-292-0/+35
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>