Difference between nfs-utils and nfs-utils-coreos

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux 9
    • nfs-utils
    • nfs-utils-coreos

Issue

  • rpc-gssd.service doesn't start automatically during boot when nfs-utils-coreos package is installed.
  • Does nfs-utils package require to start rpc-gssd.service on boot?

Resolution

  • nfs-utils-coreos is a sub package of nfs-utils which provides minimal NFS utilities for supporting clients.
  • To manage clients and daemon for the NFS server, please install nfs-utils package.

Diagnostic Steps

  • When NFS client has a RPM nfs-utils-coreos installed rpc-gssd will not start during boot and service can not
    be enabled. However service can be started manually.
  • The following message is working as designed:
# systemctl enable rpc-gssd.service
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.

Possible reasons for having this kind of units are :

 - A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory.
 - A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it.
 - A unit may be started when needed via activation (socket, path, timer,D-Bus, udev, scripted systemctl call, ...).
 - In case of template units, the unit is meant to be enabled with some instance name specified.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments