From: Niels Thykier <niels@thykier.net>
To: 852395@bugs.debian.org, Daniel Pocock <daniel@pocock.pro>,
Robbie Harwood <rharwood@club.cc.cmu.edu>
Cc: Debian kernel team <debian-kernel@lists.debian.org>, daf@debian.org
Subject: Re: Bug#852395: unblock: gssproxy/0.5.1-2
Date: Wed, 05 Apr 2017 10:37:00 +0000 [thread overview]
Message-ID: <a2f29e78-6652-e184-16c8-e68d49c639c6@thykier.net> (raw)
In-Reply-To: <87o9wwcz8j.fsf@notabene.neil.brown.name>
NeilBrown:
> On Sun, Mar 05 2017, Daniel Pocock wrote:
>
>> [...]
>
> Yes, they can.
> The systemd unit files are designed so that svcgssd will only be started
> if gssproxy didn't start - and gssproxy is tried first.
>
> If you use something other than systemd, similar logic would be needed.
>
> NeilBrown
>
>
> [...]
Hi,
@Neil: Thanks for the clarification. :) I am taking you and linux-nfs
off again (BCC'ed) as I assumed the rest follows from here are less like
to be relevant for you.
@Robbie: Can you clarify what happens for people who have chosen to use
sysvinit as init system? Will they end up with gssproxy or svcgssd or a
broken NFS?
Thanks,
~Niels
prev parent reply other threads:[~2017-04-05 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <148524180980.26332.422684345851896222.reportbug@kirtar>
[not found] ` <8ed20c71-d7e2-72e1-a8ce-c913f8e0fffd@thykier.net>
[not found] ` <17e5fbd0-9bb1-d7fa-6056-8adbda8a1f4d@pocock.pro>
[not found] ` <e157cdda-35b6-8643-7d9f-da79faec56f7@thykier.net>
[not found] ` <5df78805-b791-0a5e-3dcb-99792d78c3bd@thykier.net>
2017-03-05 19:09 ` Bug#852395: unblock: gssproxy/0.5.1-2 Daniel Pocock
2017-03-20 5:07 ` NeilBrown
2017-04-05 10:37 ` Niels Thykier [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=a2f29e78-6652-e184-16c8-e68d49c639c6@thykier.net \
--to=niels@thykier.net \
--cc=852395@bugs.debian.org \
--cc=daf@debian.org \
--cc=daniel@pocock.pro \
--cc=debian-kernel@lists.debian.org \
--cc=rharwood@club.cc.cmu.edu \
/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).