Bug 1380176 - RFE: Add reload support for quassel to systemd quassel.service
Summary: RFE: Add reload support for quassel to systemd quassel.service
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: quassel
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christian Dersch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-28 20:46 UTC by Gary T. Giesen
Modified: 2019-08-01 14:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-01 14:00:45 UTC
Type: Bug


Attachments (Terms of Use)

Description Gary T. Giesen 2016-09-28 20:46:27 UTC
Description of problem:
Systemd service file for quassel does not support the reload command

Version-Release number of selected component (if applicable):
0.12.4-1

How reproducible:
Always

Steps to Reproduce:
1. # systemctl reload quassel

Actual results:
Failed to reload quassel.service: Job type reload is not applicable for unit quassel.service.

Expected results:
Service is HUP'd

Additional info:
Probably just need to add the following to quassel.service:

ExecReload=/bin/kill -HUP $MAINPID

Comment 1 Gary T. Giesen 2016-09-28 20:56:32 UTC
Also note you probably don't need PIDFile=/var/run/quassel.pid as Quassel does not write out a PID file, and systemd won't write to the file, only read from it.

Comment 2 Gary T. Giesen 2016-09-28 21:30:40 UTC
My apologies, I just discovered Quassel currently shuts down on SIGHUP. Perhaps reserve this for when quassel 0.13 is out (due shortly) as it supports SIGHUP.

Comment 3 Ben Rosser 2018-11-19 16:16:13 UTC
quassel 0.13 is (finally) out, so I'll add the ExecReload command to the service file as suggested. Thanks for filing the ticket!

Comment 4 Ben Rosser 2019-08-01 14:00:45 UTC
This has been fixed for a while now, and Fedora 30 is out with quassel 0.13!


Note You need to log in before you can comment on or make changes to this bug.