Received: from pch.mit.edu (PCH.MIT.EDU [18.7.21.90]) by krbdev.mit.edu (8.9.3p2) with ESMTP id XAA25187; Thu, 19 Jan 2006 23:21:18 -0500 (EST) Received: from pch.mit.edu (pch.mit.edu [127.0.0.1]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id k0K4Kmei020573 for ; Thu, 19 Jan 2006 23:20:48 -0500 Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id k0K4Klei020564 for ; Thu, 19 Jan 2006 23:20:47 -0500 Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id k0K4KgLd026866; Thu, 19 Jan 2006 23:20:43 -0500 (EST) Received: from all-in-one.mit.edu (ALL-IN-ONE.MIT.EDU [18.18.1.71]) (authenticated bits=56) (User authenticated as raeburn@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.1/8.12.4) with ESMTP id k0K4KaXU025946 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 19 Jan 2006 23:20:36 -0500 (EST) Received: (from raeburn@localhost) by all-in-one.mit.edu (8.12.9) id k0K4Kaqu032236; Thu, 19 Jan 2006 23:20:36 -0500 To: krb5-bugs@MIT.EDU Subject: default profile path From: Ken Raeburn Date: Thu, 19 Jan 2006 23:20:35 -0500 Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 1.217 X-Spam-Level: * (1.217) X-Spam-Flag: NO X-Scanned-BY: MIMEDefang 2.42 X-Beenthere: krb5-bugs-incoming@mailman.mit.edu X-Mailman-Version: 2.1.6 Precedence: list Sender: krb5-bugs-incoming-bounces@PCH.mit.edu Errors-To: krb5-bugs-incoming-bounces@PCH.mit.edu X-RT-Original-Encoding: us-ascii Content-Length: 691 On most UNIX platforms, the default profile path (DEFAULT_PROFILE_PATH in osconf.h) has the system-wide version (/etc/krb5.conf) ahead of the installation-specific one (@SYSCONFDIR/krb5.conf). Since we don't install this config file, any krb5.conf found in $sysconfdir is going to have to have been supplied by the sysadmin, or whoever installed the executables. So, shouldn't we check for the installation-specific one first, ahead of the one shared by all installations? Granted, it'll be a wee bit slower in the normal case since we'd stat the non-existent file before seeing that /etc/krb5.conf hasn't changed since the last time we looked, but I don't think it'd be a big deal. Ken