[systemd-devel] [PATCH][V2] rpcbind.service: Not pulling the rpcbind.target

Steve Dickson steved at redhat.com
Fri Dec 15 13:00:47 UTC 2017


According to systemd.special(7) manpage:

rpcbind.target
    The portmapper/rpcbind pulls in this target and orders itself
    before it, to indicate its availability. systemd automatically
    adds dependencies of type After= for this target unit to
    all SysV init script service units with an LSB header
    referring to the "$portmap" facility.

Signed-off-by: Steve Dickson <steved at redhat.com>
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1431574
---
 systemd/rpcbind.service.in | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/systemd/rpcbind.service.in b/systemd/rpcbind.service.in
index f8cfa9f..9dbc82c 100644
--- a/systemd/rpcbind.service.in
+++ b/systemd/rpcbind.service.in
@@ -6,8 +6,8 @@ RequiresMountsFor=@statedir@
 
 # Make sure we use the IP addresses listed for
 # rpcbind.socket, no matter how this unit is started.
-Wants=rpcbind.socket
-After=rpcbind.socket
+Requires=rpcbind.socket
+Before=rpcbind.target
 
 [Service]
 Type=notify
-- 
2.14.3



More information about the systemd-devel mailing list