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 Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:00 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
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

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:00 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/quassel/issues/1
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.

   quassel.log (1.7 KiB)
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...