Date: Sat, 7 Jan 2017 11:27:46 +1100 (EST) From: Dave Horsfall <dave@horsfall.org> To: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: portsnap temporary files Message-ID: <alpine.BSF.2.20.1701071124100.86981@aneurin.horsfall.org> In-Reply-To: <CAGMYy3uMJZvO4xc_DL-ziff8GLGcUYber9ywWH=5397kZdQJ8Q@mail.gmail.com> References: <alpine.BSF.2.20.1701070651050.86981@aneurin.horsfall.org> <20170106223050.0fcbed48@raksha.tavi.co.uk> <CAJuc1zMVBfHo2eL5dKH8=ZkwSzsaLK=wywuV1B0r4kcOE%2B_UYg@mail.gmail.com> <alpine.BSF.2.20.1701071023560.86981@aneurin.horsfall.org> <CAGMYy3uMJZvO4xc_DL-ziff8GLGcUYber9ywWH=5397kZdQJ8Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 6 Jan 2017, Xin LI wrote: > Because the files are still being used? What makes you believe they are > unused, by the way? How would I tell? Some were there since last October, surviving a few reboots... What I do see is the INDEX file containing "...|$tmpfile"; could that be the problem? That INDEX hadn't been cleaned out for some reason? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1701071124100.86981>