On Feb 7, 2007, at 9:32 PM, Noah wrote:
From rc.conf(5):
clear_tmp_enable
(bool) Set to ``YES'' to have /tmp cleaned at
startup.
Why not setup a parallel (background) task with a wrapper script
to delete some files when upgrading ports? Either that or find a
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
On Wed, Feb 07, 2007 at 09:32:53PM -0800, Noah wrote:
From rc.conf(5):
clear_tmp_enable
(bool) Set to ``YES'' to have /tmp cleaned at startup.
Why not setup a parallel (background) task with a wrapper script to
delete some files when upgrading ports? Either
On Wed, 07 Feb 2007 21:32:53 -0800
Noah [EMAIL PROTECTED] wrote:
From rc.conf(5):
clear_tmp_enable
(bool) Set to ``YES'' to have /tmp cleaned at
startup.
And also daily_clean_tmps_enable (in periodic.conf)
Why not setup a parallel (background) task with
RW writes:
clear_tmp_enable
(bool) Set to ``YES'' to have /tmp cleaned at
startup.
And also daily_clean_tmps_enable (in periodic.conf)
Before doing this, understand the consequences,
There's stuff in my /tmp ... I understand /who/ put it
On Thu, 8 Feb 2007 10:59:28 -0500
Robert Huff [EMAIL PROTECTED] wrote:
RW writes:
clear_tmp_enable
(bool) Set to ``YES'' to have /tmp cleaned at
startup.
And also daily_clean_tmps_enable (in periodic.conf)
Before doing this, understand the
I sym linked /tmp to /var/tmp things are happy.
thank you for everybody's help.
cheers,
Noah
RW wrote:
On Wed, 07 Feb 2007 21:32:53 -0800
Noah [EMAIL PROTECTED] wrote:
From rc.conf(5):
clear_tmp_enable
(bool) Set to ``YES'' to have /tmp cleaned at
startup.
Hi there,
/tmp is filling from portmanager is placing .db information and build
details during its run.
what options to I have to alleviate the troubles this creates?
Cheers,
Noah
___
freebsd-questions@freebsd.org mailing list
On Wednesday February 07, 2007 at 06:43:15 (PM) Noah wrote:
/tmp is filling from portmanager is placing .db information and build
details during its run.
what options to I have to alleviate the troubles this creates?
Erase them. Besides how much trouble can they be causing?
Honestly,
Hi,
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
are there other solutions?
what
On Wed, Feb 07, 2007 at 03:43:15PM -0800, Noah wrote:
Hi there,
/tmp is filling from portmanager is placing .db information and build
details during its run.
what options to I have to alleviate the troubles this creates?
Well, you could move /tmp to a bigger space.
I think it is
Noah wrote:
Hi,
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
are there other
Jerry McAllister writes:
/tmp is filling from portmanager is placing .db information
and build details during its run.
what options to I have to alleviate the troubles this creates?
Well, you could move /tmp to a bigger space.
I think the best practice would be to a)
From rc.conf(5):
clear_tmp_enable
(bool) Set to ``YES'' to have /tmp cleaned at startup.
Why not setup a parallel (background) task with a wrapper script to
delete some files when upgrading ports? Either that or find a (more)
free partition and symlink /var/tmp to
14 matches
Mail list logo
