From owner-freebsd-ports@freebsd.org Fri Jan 6 20:26:23 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4BB8FCA2443 for ; Fri, 6 Jan 2017 20:26:23 +0000 (UTC) (envelope-from ohauer@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A790C1438 for ; Fri, 6 Jan 2017 20:26:22 +0000 (UTC) (envelope-from ohauer@gmx.de) Received: from [192.168.100.100] ([87.139.233.65]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Ledpu-1cqLWX1MQY-00qQJq; Fri, 06 Jan 2017 21:26:19 +0100 Subject: Re: portsnap temporary files To: FreeBSD Ports References: From: olli hauer Cc: Dave Horsfall Message-ID: <5d95e085-4f4b-3f31-bc66-0442f9d8b003@gmx.de> Date: Fri, 6 Jan 2017 21:27:56 +0100 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:q72Nm+Wx4bNtc3CqhDtgj5GazJyRHevwgeHd02rlYKNr2H3hbjI 3kXawj6cL9mFZDtV/ghoUumgJJvp4uxp6ORLtUKqQn5hTUK4obSIAwrpOcJqqCBc/6OOTbt 59Fy+eJYHpEq4b4S6y8+78Z3bVxoIISVmJmHtsHKgDvOW/q4+yjxIdXHo26393wKgUnBNEn GgKujBHt+i8pPlIquvzkQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:3jFsuehfowg=:4gfWIb/YJhn3TTNGm/fwyE AAWLqFhj7z8fhqv8SfdAgVX4Sgz16Jg7P8+08RdzewVYWozXqeYlfNKaj4f28ki1902Kl2R6j f/Je6v/fj6kOFdQCq8ejMu0QQ0OR/+wQiH3f7xK3kjVtdinnqSR0eSFNpn949BE6xKZTs4Lm4 z/vJBhm8P/u8Ss3QF5CRgFtE1yZx9Mg5xCmYYJxLkTe93gIShJsI0pZZpRj30sg4RJ4kA0Q0T O3r8FiaY89GndJsYgG4dnrMSZ1g5CcUouiKVB70zStl3ds7PBPFrkIbY9fCYj0HFbSRNqPiH/ yGPolH71oJyLeThx7oWM6q0xi7qMgKSuFKOr/K0K8SWnm0dT4NnhsyN9r58hWmlE+4bbrLQO1 V/wFwTQiYQhqOimSDiNungAgDAmiA6NCgMeBI0J/NYcJn6syhMoKzTbeQhO8gJCKrgVANYaQs vec4l7pxtto4R8R8Z2SGvYk+tjKM5/TwSWUvGOvbaktDdsBuWKh1OfbKVjBqsHFZ8M4xvVmAs Gf84pTrBLRbC+E10f9xr5UIa6kusatBNbRGo0pZn7Z3iPzcLbVwZoUHeIEK2VJu+IUogWs45B JeDy5EojlZRxSmPPY9SttNx5NoFa6vrIP1oZBzG9Ovpo07/V8Rh8zdcPmPklmrn1rTXm6H8DY qwRPOL+PBb/U5VdlPCG4bh7PHd2bpFi8XAki60Adi7r+YZYFlwIMgIOzuYQpbhXIyuDKyWJid 9JA38h+Wga3MtgV1spoeUql1sNBoj0B+/ogmkRuTVeFKOjTJfOF5MQpTpTIwiq62uiaCOmVRx UWSNWwo X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2017 20:26:23 -0000 On 2017-01-06 20:51, Dave Horsfall wrote: > Is there some reason why portsnap cannot clean up /var/db/portsnap/files? > I've just had to remove a zillion of them, a bunch at a time because "rm" > choked on the arg list. > > Perhaps a "portsnap clean" command? I'm surprised that there isn't one. > Why? As soon you run "portsnap fetch" old files in this directory are purged! If you look into /var/db/portsnap/INDEX you can see the mapping of the files I'm running portsnap on one system since portsnap was introduced and never had issues with cleanups. -- olli