[16339] in Kerberos_V5_Development
Re: KDC worker processes project
daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Sep 17 15:21:07 2010
From: Greg Hudson <ghudson@mit.edu>
To: Ken Raeburn <raeburn@mit.edu>
In-Reply-To: <D01C984F-E25B-4F09-9C6B-C57472341CF2@mit.edu>
Date: Fri, 17 Sep 2010 15:20:58 -0400
Message-ID: <1284751258.5992.1810.camel@ray>
Mime-Version: 1.0
Cc: "krbdev@mit.edu Dev List" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Fri, 2010-09-17 at 14:34 -0400, Ken Raeburn wrote:
> I find the disabling of automatic handling of network reconfiguration
> based on platform plus whether you're using worker processes rather
> unappealing
It's not great, but:
(1) Fundamentally, the onus is on the operating system here. The basic
BSD sockets API makes it impossible to implement RFC 1123 section 2.3
semantics for UDP servers, and there's a limit to how much complexity
every UDP server should have to re-implement to work around that
failure--especially given that there is a well-known extension (pktinfo)
making that complexity unnecessary, and this extension is implemented on
some of the most popular Unix-like platforms.
(2) The overlap between "needs the scalability of worker processes" and
"is expected to add network interfaces the KDC cares about" seems
nonexistent. If you're running a KDC serving a large volume of
requests, it's unlikely that you're doing so over a DHCP network
interface.
> It shouldn't be that tough to do.
It's too tough for me to do in the timeline we have available. I won't
object if you want to do the work.
The plan you suggest is not simple to carry out. Currently the
supervisor spends its time a wait() loop in the KDC's main.c not the
select() loop of net-server.c.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
