Date: Sat, 03 Mar 2012 20:26:21 +0400 From: Yuri Pankov <yuri.pankov@gmail.com> To: Chris Rees <crees@freebsd.org> Cc: Rotate 13 <rabgvzr@gmail.com>, freebsd-current@freebsd.org Subject: Re: src.conf ignored; phantom named Message-ID: <4F52462D.6080802@gmail.com> In-Reply-To: <CADLo83-7La=q4-HMZV_0nMObtZ_qxg7dKtEN_Vy28igYZOPixw@mail.gmail.com> References: <CADBSp1fwsbx96wZ1B7MXtNbkY1V78ASCRxqgx3iVJVOFscbmVw@mail.gmail.com> <4F515316.8080904@gmail.com> <CADLo83-7La=q4-HMZV_0nMObtZ_qxg7dKtEN_Vy28igYZOPixw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 3 Mar 2012 15:43:44 +0000, Chris Rees wrote: > On 2 March 2012 23:09, Yuri Pankov<yuri.pankov@gmail.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F52462D.6080802>