Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by krbdev.mit.edu (Postfix) with ESMTP id 3D0083E626 for ; Fri, 25 May 2012 11:28:57 -0400 (EDT) Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q4PFSuV3032063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 25 May 2012 11:28:57 -0400 Received: from blade.bos.redhat.com (blade.bos.redhat.com [10.16.184.36]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q4PFSuPX003689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 25 May 2012 11:28:56 -0400 Received: from blade.bos.redhat.com (localhost.localdomain [127.0.0.1]) by blade.bos.redhat.com (8.14.5/8.14.5) with ESMTP id q4PFStqH013946 for ; Fri, 25 May 2012 11:28:55 -0400 Received: (from nalin@localhost) by blade.bos.redhat.com (8.14.5/8.14.5/Submit) id q4PFSt3m013945 for rt-comment@krbdev.mit.edu; Fri, 25 May 2012 11:28:55 -0400 Date: Fri, 25 May 2012 11:28:55 -0400 From: Nalin Dahyabhai To: Nico Williams via RT Subject: Re: [krbdev.mit.edu #6742] would like to be able to specify listening address for krb5kdc and kadmind Message-ID: <20120525152854.GA13202@redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Red Hat, Inc. X-Disclaimer: I am not a spokesmodel. Views expressed are my own. X-Key-ID: 78688BF5 X-Key-Fingerprint: 60BC AD87 AF51 3A00 8C99 0388 379B CE57 7868 8BF5 User-Agent: Mutt/1.5.21 (2010-09-15) X-Scanned-BY: MIMEDefang 2.68 on 10.5.11.23 RT-Send-Cc: X-RT-Original-Encoding: us-ascii Content-Length: 637 On Fri, May 25, 2012 at 03:14:10AM -0400, Nico Williams via RT wrote: > The way inetd starts wait services is so ingrained into daemons that > support inetd that any change to it would have to be optional and would > take a long time to be adopted. Still, if you can find an inetd daemon > that can do this then we could make krb5kdc support it. The one I had in mind was systemd: http://www.freedesktop.org/software/systemd/man/systemd.socket.html In newer releases we still start the daemons as regular services, but being able to have systemd wait to fire them up until clients first attempt to talk to them could be handy. Nalin