From owner-freebsd-current@FreeBSD.ORG Sat Mar 3 16:26:31 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 A6315106566C; Sat, 3 Mar 2012 16:26:31 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id D83E88FC16; Sat, 3 Mar 2012 16:26:30 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so3003084bkc.13 for ; Sat, 03 Mar 2012 08:26:30 -0800 (PST) Received-SPF: pass (google.com: domain of yuri.pankov@gmail.com designates 10.204.129.23 as permitted sender) client-ip=10.204.129.23; Authentication-Results: mr.google.com; spf=pass (google.com: domain of yuri.pankov@gmail.com designates 10.204.129.23 as permitted sender) smtp.mail=yuri.pankov@gmail.com; dkim=pass header.i=yuri.pankov@gmail.com Received: from mr.google.com ([10.204.129.23]) by 10.204.129.23 with SMTP id m23mr7245669bks.134.1330791990001 (num_hops = 1); Sat, 03 Mar 2012 08:26:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=xCAqOKAOOMV7QejUQeZV0OTpNR8dR5Pd1uAq0LEd3Cc=; b=EspOBnsFlI5Zuk1PCWi0vRSZVbpfDyUMju4M4yR8ceg4fns8Ob53ooJBhm6OffWqOW f5oRsNDR+Rg3kJOV+4hb6EH9HnViAzgMBylPV7bg0wRDTVX2A0PFPB0g51yTn6DA9NlV rRnyBQvtbZiAPSxHaJdiNhpVjiJuV1XAxmvv9CCa9VQRVuLZCX5E90NDX891CbruPYZF C53+vN3SxkPBpwLHUoCKCmDocVPkva+1uLlUh862lC87dpyzrP0e4EX4ELfKQAjgPdrE ru6TRmpgR2NoHW3oWLW1J1K3L51du5Id2cLZDbGAOo0L5Hyr8YPLaavyu20A4Q9dbHVw hB9A== Received: by 10.204.129.23 with SMTP id m23mr5785660bks.134.1330791989823; Sat, 03 Mar 2012 08:26:29 -0800 (PST) Received: from [192.168.1.4] ([213.132.76.142]) by mx.google.com with ESMTPS id je3sm15261221bkb.15.2012.03.03.08.26.27 (version=SSLv3 cipher=OTHER); Sat, 03 Mar 2012 08:26:28 -0800 (PST) Message-ID: <4F52462D.6080802@gmail.com> Date: Sat, 03 Mar 2012 20:26:21 +0400 From: Yuri Pankov User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Chris Rees References: <4F515316.8080904@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 16:26:31 -0000 On Sat, 3 Mar 2012 15:43:44 +0000, Chris Rees wrote: > 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="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? I have been combing over >>> makefiles under /usr/src (not to mention, going through /etc/rc.d/ >>> trying to figure out what actually started named). As far as I >>> ascertain, _WITHOUT_SRCCONF is *not* set anywhere for world building; >>> named_enable="no" in relevant rc.conf files; rpcbind and ntpd are not >>> running either. Since 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 root@xyz.example.com:/usr/obj/usr/src/sys/CUSTOM >>> 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. ObsoleteFiles.inc also includes tools/build/mk/OptionalObsoleteFiles.inc, which defines the file lists for various WITH_|WITHOUT_ options.