Bug 730129
Summary: | Logrotate script for mumble server uses non-existent command. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mike Lilley <lilley.rpm> |
Component: | mumble | Assignee: | Christian Krause <chkr> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 15 | CC: | chkr, j.golderer, th0br0 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-19 15:02:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mike Lilley
2011-08-11 20:39:26 UTC
Just wondering if there are any plans to fix this bug? I've changed my logrotate script to simply read "service murmur restart" instead of the start-stop-daemon line, and it seems to work fine. However, I got involved with an SELinux bug involving logrotate and murmur, so I thought I'd see if this was gonna get fixed. (In reply to comment #1) > Just wondering if there are any plans to fix this bug? I will fix this in the next update of mumble/murmur. > I've changed my logrotate script to simply read "service murmur restart" > instead of the start-stop-daemon line, and it seems to work fine. However, > I got involved with an SELinux bug involving logrotate and murmur, so I > thought I'd see if this was gonna get fixed. There is no need to restart murmur entirely and indeed the existing script using the start-stop-daemon just sent a SIGHUP to the daemon. I will use the following scriptlet: /bin/kill -HUP `cat /var/run/mumble-server/mumble-server.pid 2>/dev/null` 2> /dev/null || true mumble-1.2.3-7.fc17.1 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/mumble-1.2.3-7.fc17.1 mumble-1.2.3-5.fc16.1 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/mumble-1.2.3-5.fc16.1 mumble-1.2.3-4.fc15.1 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/mumble-1.2.3-4.fc15.1 Package mumble-1.2.3-4.fc15.1: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mumble-1.2.3-4.fc15.1' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-8960/mumble-1.2.3-4.fc15.1 then log in and leave karma (feedback). mumble-1.2.3-5.fc16.1 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. mumble-1.2.3-4.fc15.1 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. mumble-1.2.3-7.fc17.1 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. (In reply to comment #2) > (In reply to comment #1) > I will fix this in the next update of mumble/murmur. Thanks, Christian! |