Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#48379 - [quassel-core] conf.d is ignored

Attached to Project: Community Packages
Opened by Justin Dray (justin8) - Tuesday, 01 March 2016, 00:47 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 01 March 2016, 18:49 GMT
Task Type Bug Report
Category Packages
Status Assigned
Assigned To Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

Description:
Changing the LISTEN value in conf.d is totally ignored by the service.

Additional info:
* package version(s)
0.12.3-1
* config and/or log files etc.


Steps to reproduce:
1. Modify /etc/conf.d/quassel.conf
2. Restart systemd service
3. Observe no changes
This task depends upon

Comment by Doug Newgard (Scimmia) - Tuesday, 01 March 2016, 18:48 GMT
Does it work if you stop the service, do `systemctl daemon-reload`, then start it again? If not, got logs?
Comment by Justin Dray (justin8) - Tuesday, 01 March 2016, 22:05 GMT
Well, the config file has LISTEN=127.0.0.1 and on first run it tries to listen on 0.0.0.0

Doesn't daemon-reload only affect changes to units? I thought the config files were sourced each time it was run.
Comment by Justin Dray (justin8) - Tuesday, 01 March 2016, 22:07 GMT
cat /etc/conf.d/quassel
QUASSEL_USER=quassel
LISTEN=0.0.0.0

And the logs are attached for the last run. The port conflict is because it uses the same port as crashplan, which was why I wanted to change the config file in the first place.

Loading...