Red Hat Bugzilla – Bug 804891
rstatd/rusersd killed by systemd
Last modified: 2012-04-13 17:31:01 EDT
Description of problem:
rstatd/rusersd won't stay up for more than about 2 minutes, then systemd kills it
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. systemctl start rstatd.service
2. note this doesn't return for 2 minutes; note rstatd runs for 2 minutes
3. note rstatd is no longer running after 2 minutes
repeat for rusersd; same deal
/lib/systemd/system/rstatd.service has been configured with the
PIDFile=/var/run/rstatd.pid parameter, telling systemd to expect a pid
file when rstatd is happy.
However rstatd never writes a pid file, so systemd kills it after 2 minutes.
Same deal with rusersd.
In prior Fedora releases, the /etc/init.d/rstatd script did a 'touch
/var/run/rstatd.pid' for completeness. Similar with rusersd.
The fix is to remove the PIDFile arg from /lib/systemd/system/rstatd.service,
or to modify rstatd source to get it to write a pid file.
Similar with rusersd.
This bug is of the same nature as https://bugzilla.redhat.com/show_bug.cgi?id=804880
rusers-0.17-68.fc17 has been submitted as an update for Fedora 17.
rusers-0.17-68.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rusers-0.17-68.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Fix in fc16 package seems fine to me. Can't test fc17 version right now.
rusers-0.17-68.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
rusers-0.17-68.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.