From owner-freebsd-ports@FreeBSD.ORG Tue Aug 12 18:11:36 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8AAE4AC5 for ; Tue, 12 Aug 2014 18:11:36 +0000 (UTC) Received: from astart2.astart.com (108-248-95-193.lightspeed.sndgca.sbcglobal.net [108.248.95.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 37CD63AC9 for ; Tue, 12 Aug 2014 18:11:35 +0000 (UTC) Received: from laptop_93.private (localhost [127.0.0.1]) by astart2.astart.com (8.14.4/8.14.4) with ESMTP id s7CIBGDP085680 for ; Tue, 12 Aug 2014 11:11:20 -0700 (PDT) (envelope-from papowell@astart.com) Message-ID: <53EA58C5.6020509@astart.com> Date: Tue, 12 Aug 2014 11:11:17 -0700 From: Patrick Powell Reply-To: papowell@astart.com Organization: Astart Technologies User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: 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> <53DF69ED.4040700@cyberbotx.com> <20140804112821.GF1228@albert.catwhisker.org> <53E56488.1070104@cyberbotx.com> <53E6C7A9.30104@cyberbotx.com> In-Reply-To: <53E6C7A9.30104@cyberbotx.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2014 18:11:36 -0000 On 08/09/14 18:15, Naram Qashat wrote: > On 08/09/14 19:45, Scot Hetzel wrote: >> On Fri, Aug 8, 2014 at 7:00 PM, Naram Qashat >> wrote: >>> On 08/04/14 07:28, David Wolfskill wrote: >>>> >>>> On Mon, Aug 04, 2014 at 07:09:33AM -0400, Naram Qashat wrote: >>>>> >>>>> 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 >>>>> >>>>> ... >>>>> This was a really good suggestion..... >>>> >>>> >>>> Glad to help. :-) >>>> >>>> Peace, >>>> david >>> >>> >>> OK, so while no programs have whined or complained, I get the >>> feeling that >>> something on my system is running portsnap without my knowledge. >>> When I had >>> set the schg flag on INDEX-9, an INDEX-9.bz2 file came up. I set the >>> schg >>> flag on that as well, and now I notice there are a bunch of files >>> called >>> .fetch.??????.INDEX-9.bz2 (where ?????? is a random string), as well >>> as a >>> file called .portsnap.INDEX. As far as I know, I don't have anything >>> configured to run portsnap, but is there something that defaults to >>> running >>> portsnap occasionally? I couldn't find anything that would do that. >>> >> >> Do your have a crontab entry that is running portsnap with the -I >> (update INDEX) option? >> >> http://www.pl.freebsd.org/doc/handbook/portsnap.html > > As far as I can tell, no, none of my crontabs have any references to > portsnap in them. This is making me a bit stumped as to why it would > be happening. I checked the main /etc/crontab, I checked the crontabs > in /var/cron/tabs. I have searched inside of /etc and /usr/local/etc > for anything related to portsnap. Nothing that would be doing this is > coming up at all. > > Thanks, > Naram Qashat > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > I ran into something similar once, and found out what was happening this way. 1. replace the portsnap executable with a shell script. Rename portsnap to something like /usr/sbin/portsnap.orig 2. This shell script should dump the current ENV and other stuff to a log file. Don't forget to put in a timestamp. And then do: exec /usr/sbin/portsnap.orig $* I did this and found that there was something in one of the .login scripts. Grrrr...