Date: Mon, 04 Aug 2014 07:09:33 -0400 From: Naram Qashat <cyberbotx@cyberbotx.com> To: David Wolfskill <david@catwhisker.org>, freebsd-ports@FreeBSD.org Subject: Re: Does pkg automatically download INDEX? Message-ID: <53DF69ED.4040700@cyberbotx.com> In-Reply-To: <20140804021418.GE1228@albert.catwhisker.org> References: <53DE7266.5000606@cyberbotx.com> <53DE8623.1090208@infracaninophile.co.uk> <53DE8EBD.4090303@cyberbotx.com> <53DE934C.101@FreeBSD.org> <53DE9B38.2000805@cyberbotx.com> <CAN6yY1tu-M1g6h3ihmOxd=dTrVQHccTWrXZPkn-dmcPteTo4vg@mail.gmail.com> <53DEEB93.8010208@cyberbotx.com> <20140804021418.GE1228@albert.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53DF69ED.4040700>