Description of problem: The options to /usr/bin/mlnet are hard-coded into the systemd service file, therefore the mldonkey server always gets started with '/usr/bin/mlnet -log_to_syslog yes -log_file /dev/null -pid /run/mldonkey' regardless of the options set in /etc/sysconfig/mldonkey Version-Release number of selected component (if applicable): mldonkey-server-3.0.3-5.fc18.x86_64 How reproducible: Always Steps to Reproduce: 1. systemctl start mldonkey.service 2. change anything in /etc/sysconfig/mldonkey 3. systemctl restart mldonkey.service Actual results: The server is always started logging to syslog and using /var/lib/mldonkey as config directory Expected results: Depending on the environment variables in /etc/sysconfig/mldonkey the server should be started respecting those options Additional info: I'm no systemd expert, but /usr/lib/systemd/system/mldonkey.service should look something like this: [Service] User=mldonkey EnvironmentFile=/etc/sysconfig/mldonkey ExecStart=/usr/bin/mlnet -log_to_syslog $LOG_TO_SYSLOG -log_file $LOGFILE -pid /run/mldonkey
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Is this a joke? Come on guys, it's been a year. The fix takes about 5 minutes. Pretty please with sugar on top.
Why not become a packager, then you can do the fix yourself?
mldonkey-3.1.3-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mldonkey-3.1.3-3.fc19
mldonkey-3.1.3-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mldonkey-3.1.3-3.fc18
mldonkey-3.1.3-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mldonkey-3.1.3-3.fc20
Package mldonkey-3.1.3-3.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mldonkey-3.1.3-3.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-15951/mldonkey-3.1.3-3.fc20 then log in and leave karma (feedback).
mldonkey-3.1.3-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
mldonkey-3.1.3-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
mldonkey-3.1.3-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.