Red Hat Bugzilla – Bug 747363
rpcbind ships a systemd socket unit but does not support socket activation
Last modified: 2014-12-17 10:14:51 EST
Tom Gundersen (tomegun) on #systemd noticed:
does anyone know the status of rpcbind? i notice that fedora ships with
native service/socket files, but as far as i can tell mezcalero's socket
activation patches were never merged upstream... how can this work? am i
I agree with him. Lennart's patch http://www.spinics.net/lists/linux-nfs/msg14371.html was never merged to rpcbind.
"grep -r sd_listen rpcbind-0.2.0/" in the prepped Fedora tree finds nothing.
How can rpcbind.socket in F16 do anything useful? Are not the systemd and rpcbind processes fighting over /var/run/rpcbind.sock?
An updated version of the socket activation patch was posted to linux-nfs by Tom Gundersen:
For what it's worth, an updated patch is available here:
http://www.spinics.net/lists/linux-nfs/msg26364.html (the first one had some bugs).
If you are not going to add socket activation support to rpcbind in F16, please at least remove rpcbind.socket (and the reference to it in rpcbind.service) from the package.
Its presence without the corresponding support in the daemon is harmful.
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.
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 16'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 16 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 to click on
"Clone This Bug" and open it against that version of Fedora.
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.
The process we are following is described here:
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
From inspection of the code it looks like this patch still isn't applied. And it looks like bug 1158164 might be a symptom.
rpcbind-0.2.2-0.0.fc21 has been submitted as an update for Fedora 21.
rpcbind-0.2.2-0.0.fc20 has been submitted as an update for Fedora 20.
* 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 rpcbind-0.2.2-0.0.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
rpcbind-0.2.2-0.0.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
rpcbind-0.2.2-1.0.fc20 has been submitted as an update for Fedora 20.