From owner-freebsd-ports@FreeBSD.ORG Mon Aug 4 11:09:37 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9C9AA5F8 for ; Mon, 4 Aug 2014 11:09:37 +0000 (UTC) Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by mx1.freebsd.org (Postfix) with ESMTP id 490CA28C8 for ; Mon, 4 Aug 2014 11:09:37 +0000 (UTC) Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta04.westchester.pa.mail.comcast.net with comcast id aasB1o00116LCl054b9bvr; Mon, 04 Aug 2014 11:09:35 +0000 Received: from kirby.cyberbotx.com ([107.5.48.95]) by omta06.westchester.pa.mail.comcast.net with comcast id ab9Z1o00N23DSHF3Sb9aSg; Mon, 04 Aug 2014 11:09:35 +0000 Message-ID: <53DF69ED.4040700@cyberbotx.com> Date: Mon, 04 Aug 2014 07:09:33 -0400 From: Naram Qashat User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: David Wolfskill , freebsd-ports@FreeBSD.org Subject: Re: Does pkg automatically download INDEX? References: <53DE7266.5000606@cyberbotx.com> <53DE8623.1090208@infracaninophile.co.uk> <53DE8EBD.4090303@cyberbotx.com> <53DE934C.101@FreeBSD.org> <53DE9B38.2000805@cyberbotx.com> <53DEEB93.8010208@cyberbotx.com> <20140804021418.GE1228@albert.catwhisker.org> In-Reply-To: <20140804021418.GE1228@albert.catwhisker.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1407150575; bh=8AH7+tPlpdYnBOMI9Y1sGv0keQFCZCp9ROIi+hnIk1I=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=o3Xex/yYGCNa0NXVbURTPEeTogr3gYkzrDJiLRLlKjqltw+x6PVEcIpbLXgX4FTlt kPuHiw5QQ26AcWc8pY4yrJnlccjW4UGZZ6CkpBwXxa9bghJHRQr+0d4C2sxMasoKFP gzFAD8zmZWfv+vfY1PsqMx5MOBA+jgbHcKZ4wiJCkWMfAcNa1KGJJxtw3u2abbEb52 eC4dMm12yQqBG7FKqyWCM+OurBFSbxaSKYpB+gw8G1hfVnixI41JGagf+/xVJ7l/0l mPkHulYL+fHYVmPjg4RJMe8ydOh/xygyZU8eDsNPhl+XXHAH1ugs/BTpeLseBbWYpL N8oso70V0CIQA== X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2014 11:09:37 -0000 On 08/03/14 22:14, David Wolfskill wrote: > On Sun, Aug 03, 2014 at 10:10:27PM -0400, Naram Qashat wrote: >> ... >> If there is >> a way to find out when any process is attempting to modify a file, that would >> probably help me narrow it down, but I'm not aware of anything that can do that, >> ... > > Well, "chflags schg /usr/ports/INDEX*" would *prevent* the modification > -- and with luck, the offending process might whine or squawk (thus > providing you with identification). > > "chflags noschg /usr/ports/INDEX*" to undo it. > > Peace, > david This was a really good suggestion. While I wasn't lucky in regards to having a process whine about being unable to write to INDEX-9, I did find that now there is an INDEX-9.bz2 sitting in /usr/ports, which I assume comes from a download of it. I'm going to try setting INDEX-9.bz2 to also have the schg flag on it, maybe that'll make a process complain. If not, at least I can modify my manual INDEX building to remove the schg flag before updated INDEX and then setting it again afterwards. Thanks, Naram Qashat