Date: Thu, 08 Feb 2007 05:47:00 -0500 From: Gerard Seibert <gerard@seibercom.net> To: User Questions <freebsd-questions@freebsd.org> Subject: Re: /tmp getting full form portmanager Message-ID: <20070208053430.434C.GERARD@seibercom.net> In-Reply-To: <45CA7215.7030004@enabled.com> References: <20070207193234.BFA4.GERARD@seibercom.net> <45CA7215.7030004@enabled.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday February 07, 2007 at 07:43:01 (PM) Noah wrote:
> I dont think this is an adequate solution.
>
> /tmp is filling up during the portmanager run. in other words - while I
> am running /tmp fills up. so it needs to be erased periodically while
> portmanager is running or else no other packages can be downloaded
Please don't top post. If you don't know what that means, Google for it.
Exactly how much space are these files taking up? I run portmanager
weekly and have never, ever seen this phenomena. Yes, it does produce
some temporary files to keep track of what it is doing, files to be
excluded, etc., but they are relatively small. I would certainly not
recommend that you delete them while portmanager is actually running
though.
What are you referring to by: "while portmanager is running or else no
other packages can be downloaded". I can log in as a different user, or
simply run portmanager in the background and then proceed to download
files or do virtually anything else I desire, with the possible
exception of running another instance of portmanager. Exactly how are
you being affected?
Have you tried cleaning out the "/usr/ports/distfiles" directory after
doing an update? Those files are not needed any more. They can take up a
considerable amount of space.
Perhaps you could be a little more specific about what you are
attempting to do. Also, would you include the output of:
df -h
I would be interested in what your drive looks like.
--
Gerard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070208053430.434C.GERARD>