User complained that with systemd nfs is never started. What actually
happens - it is started, but too early, before rpcbind. What happens
is:
{pts/1}% grep Provides /etc/init.d/rpcbind
# Provides: $portmap
{pts/1}% grep Require /etc/init.d/nfs-common
# Required-Start: $portmap
# Required-Stop: $portmap
{pts/1}% systemctl --no-pager show -pmAfter -p Before -p Wants -p
WantedBy rpcbind.service
Wants=
WantedBy=rpcbind.target multi-user.target graphical.target
Before=rpcbind.target pppoe.service shutdown.target multi-user.target
graphical.target
{pts/1}% systemctl --no-pager show -pmAfter -p Before -p Wants -p
WantedBy nfs-common.service
Wants=
WantedBy=multi-user.target graphical.target
Before=nfs-server.service netfs.service pppoe.service shutdown.target
multi-user.target graphical.target
But nothing pulls in rpcbint.target ...
{pts/1}% systemctl --no-pager show -pmAfter -p Before -p Wants -p
WantedBy rpcbind.target
Wants=rpcbind.service
WantedBy=
Before=netfs.service nfs-common.service
How is it supposed to be activated? May be, at least for legacy case
of SysV scripts systemd should automatically add rpcinfo.target to
transaction if it sees Provides: $portmap in any active service?
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
