rpm/quassel
SHA256
1
0
Fork 0
forked from pool/quassel
Code Pull Requests Activity

Accepting request 631132 from home:rkitover:branches:KDE:Extra

Browse Source 
fix systemd ordering cycle in quasselcore.service

Previously I changed the service to After=default.target so that
postgresql has a chance to start up, in the case it is used as the
database. This seems to cause an ordering cycle causing the service to
not start on boot.

I am not sure if this was a problem before, or just started happening
with a more recent systemd.

I talked to a knowledgeable person on freenode #systemd (boucman) who
suggested using After=postgresql.service instead, there is no error if
the postgresql.service is not installed. Likewise add
After=mysql.service in case it is the database being used. If sqlite is
being used (as is the default) then After=network-online.target would be
in effect.

OBS-URL: https://build.opensuse.org/request/show/631132
OBS-URL: https://build.opensuse.org/package/show/KDE:Extra/quassel?expand=0&rev=74
This commit is contained in:
Tomáš Chvátal 2018-08-23 16:50:16 +00:00 committed by Git OBS Bridge
parent 3e3e16516c
commit 30b68738e0
2 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
quassel.changes
View File

@ -1,3 +1,8 @@
-------------------------------------------------------------------
Thu Aug 23 15:33:34 UTC 2018 - rkitover@gmail.com
- Fix systemd ordering cycle in quasselcore.service
-------------------------------------------------------------------
Tue Jul 31 11:55:31 UTC 2018 - tchvatal@suse.com

4
service.quasselcore
View File

@ -1,6 +1,8 @@
[Unit]
Description=Quassel Core
After=default.target
After=network-online.target
After=postgresql.service
After=mysql.service
[Service]
EnvironmentFile=-/etc/sysconfig/quasselcore