From owner-freebsd-current@FreeBSD.ORG Sat Mar 3 15:44:15 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 631F2106566C for ; Sat, 3 Mar 2012 15:44:15 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1E1498FC29 for ; Sat, 3 Mar 2012 15:44:14 +0000 (UTC) Received: by iahk25 with SMTP id k25so4781795iah.13 for ; Sat, 03 Mar 2012 07:44:14 -0800 (PST) Received-SPF: pass (google.com: domain of utisoft@gmail.com designates 10.50.222.135 as permitted sender) client-ip=10.50.222.135; Authentication-Results: mr.google.com; spf=pass (google.com: domain of utisoft@gmail.com designates 10.50.222.135 as permitted sender) smtp.mail=utisoft@gmail.com; dkim=pass header.i=utisoft@gmail.com Received: from mr.google.com ([10.50.222.135]) by 10.50.222.135 with SMTP id qm7mr2078280igc.9.1330789454733 (num_hops = 1); Sat, 03 Mar 2012 07:44:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=4mMt7U87XMNLVxqmJ7qMi6WfusGe3qUg8o5oI5IK0a0=; b=BmWkFj1xw5idNc5VlZSloxe4prGi4R44s1vXW/z4ERlzwcgcXDr4HRLij2fTnfCG+S ydmu2ErhZZHd0NI6OHis1IPz3G34aUhD9AmVTzW0BQBeal3j7ECRHL6jbMgLEgaJ38oP msGJeLih0PcsRlJx8f26+RAGaQS/5iguBXRNgOPQcNO3eCX99hn0ORMhYjvKbWVgBINI YPkAU6na999XI6trQBgRGidznZXQ1GGfCvs5LXzIceLURxSXGTgqMLuwzrIV7ZIfW3hu CX6mh6bODMERnJ0LhxPQfBSuno+D5VyRMWuma/fK9G9Z3L7MMUvdbFapmV9IBcF9y81I eveQ== Received: by 10.50.222.135 with SMTP id qm7mr1716035igc.9.1330789454673; Sat, 03 Mar 2012 07:44:14 -0800 (PST) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.53.67 with HTTP; Sat, 3 Mar 2012 07:43:44 -0800 (PST) In-Reply-To: <4F515316.8080904@gmail.com> References: <4F515316.8080904@gmail.com> From: Chris Rees Date: Sat, 3 Mar 2012 15:43:44 +0000 X-Google-Sender-Auth: F3WHLjaE8w9CqtUMg22HuivjerA Message-ID: To: Yuri Pankov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Rotate 13 , freebsd-current@freebsd.org Subject: Re: src.conf ignored; phantom named X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2012 15:44:15 -0000 On 2 March 2012 23:09, Yuri Pankov wrote: > On Fri, 2 Mar 2012 17:41:28 -0500, Rotate 13 wrote: > >> I set WITHOUT_BIND=3D"yes" in /etc/src.conf, and built/installed world. >> Not only does /usr/sbin/named exist - named is actually started! >> Several other WITHOUT_* variables also were apparently ignored, as >> evidenced by stuff installed on running system. >> >> My main question is - how do I debug this? =A0I have been combing over >> makefiles under /usr/src (not to mention, going through /etc/rc.d/ >> trying to figure out what actually started named). =A0As far as I >> ascertain, _WITHOUT_SRCCONF is *not* set anywhere for world building; >> named_enable=3D"no" in relevant rc.conf files; rpcbind and ntpd are not >> running either. =A0Since named daemonized, it's not easy to tell who >> started it - and grepping everything in sight, I can't figure out how >> it got built in the first place. >> >> uname -a: >> FreeBSD xyz.example.com 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Thu Feb 29 >> 10:28:17 CST 2012 =A0 =A0root@xyz.example.com:/usr/obj/usr/src/sys/CUSTO= M >> amd64 >> >> I focused substantial attention on /usr/src/share/bsd.own.mk and >> worked outward; but did not find anything obvious. >> >> Advice on where to poke for the right information, much appreciated. > > > src.conf controls what is (not) built. To actually remove the bits marked= as > WITHOUT_ from the system, try running `make delete-old` in /usr/src. Has the behaviour of make delete-old changed? As far as I can remember, it doesn't remove stuff marked as WITHOUT_ --it's there to deal with updates. Chris