linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aram Akhavan <aram@nubmail.ca>
To: linux-nfs@vger.kernel.org
Subject: Why does nfs-client.target include rpc.svcgssd?
Date: Tue, 27 Sep 2022 13:21:22 -0700	[thread overview]
Message-ID: <589498d2-6cac-47bd-8e93-8fdd44e4be45@nubmail.ca> (raw)

Hi all,

I'm a newbie starting to play around with kerberized nfs on Debian. I 
noticed that in the systemd target file nfs-client.target 
<http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=blob;f=systemd/nfs-client.target;h=8a8300a1dfc6e6a77dfe0abed9942ded8f6b0103;hb=refs/heads/master> 
has *rpc-svcgssd* among its list of dependencies. From the man pages 
<https://linux.die.net/man/8/rpc.svcgssd>, it seems this is a 
server-side daemon, not client-, and as expected I don't seem to need it 
for the clients to mount anything successfully. Why is this part of the 
client target?

I thought it may be a dependency for something else, but I haven't been 
able to find what. Similarly, why is it installed with the *nfs-common* 
package instead of *nfs-kernel-server* if it's not needed?

This came up because I kept seeing errors on boot caused by rpc.svcgssd 
looking for nfs//FQDN/@/REALM /in the keytab, but it doesn't exist. 
rpc.gssd, on the other hand, was updated 
<https://linux.die.net/man/8/rpc.gssd> to search for other principals, 
like host/FQDN@REALM, which is what gets set up in the keytab by default.

Thanks,

Aram

             reply	other threads:[~2022-09-27 20:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 20:21 Aram Akhavan [this message]
2022-09-29 16:33 ` Why does nfs-client.target include rpc.svcgssd? Chuck Lever III

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=589498d2-6cac-47bd-8e93-8fdd44e4be45@nubmail.ca \
    --to=aram@nubmail.ca \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).