From: Simo Sorce <simo@redhat.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] Centralize dependencies on the auth unit.
Date: Thu, 2 Oct 2014 16:08:22 -0400 [thread overview]
Message-ID: <20141002160822.0fa80208@willson.usersys.redhat.com> (raw)
In-Reply-To: <542DA720.5020002@RedHat.com>
On Thu, 02 Oct 2014 15:27:28 -0400
Steve Dickson <SteveD@redhat.com> wrote:
> I begrudgingly commit this because when gssproxy is install
> the NFS client will *always* start it, which is
> a bug in gssproxy... IMHO... If a daemon is not needed
> it shouldn't start up... similar to how the gss daemons work.
I agree with you that when a service is not needed it should not start,
but it is tricky to automatically figure, from init scripts, if it is
needed, because gssproxy has is a general purpose tool that can be used
for other user-space related uses and not server NFS at all.
On the bright side an admin that is annoyed by it being started can
simply mask it:
# systemctl mask gssproxy.service
or even uninstall the package for now.
Now the reason gssproxy.service is always started seem to be that
although auth-rpcgss-module.service is not going to start and it set to
start Before all its Wants ... those Wants seem to be processed and
started anyway.
I think this may be seen as a bug, we'll probably need to ask upstream
if it is or if there is some other clever workaround to Want another
unit files conditioned to whether the unit is going to be started at
runtime.
Simo.
--
Simo Sorce * Red Hat, Inc * New York
prev parent reply other threads:[~2014-10-02 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <542AC20B.9040509@redhat.com>
2014-09-30 15:44 ` [PATCH 1/1] Centralize dependencies on the auth unit Simo Sorce
2014-10-02 19:27 ` Steve Dickson
2014-10-02 20:08 ` Simo Sorce [this message]
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=20141002160822.0fa80208@willson.usersys.redhat.com \
--to=simo@redhat.com \
--cc=SteveD@redhat.com \
--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