Matthew Dillon wrote:
I think a hammerd is a good idea or more likely a 'hammer cleanup'
with a deamon-mode option that leaves it running in the background,
but operating on the disk very lightly (as in very, VERY lightly)
until the time schedule tells it that it really
I think a hammerd is a good idea or more likely a 'hammer cleanup'
with a deamon-mode option that leaves it running in the background,
but operating on the disk very lightly (as in very, VERY lightly) until
the time schedule tells it that it really has to run harder.
On Mon, Oct 18, 2010 at 9:31 PM, elekktrett...@exemail.com.au wrote:
What about hammerd?
* Starts when system starts
* Wakes up every 10 seconds or so to check current system load/memory
usage to estimate if its appropriate to run a cleanup operation at this
time.
* Can have a text file
Probably it will be nicer for desktop users to have a run when
history is using more than X space than by periodic.
On Mon, Oct 18, 2010 at 02:49, elekktrett...@exemail.com.au wrote:
I think we definitely must have hammer cleanup not depending on periodic.
Especially laptop/workstation users,
elekktrett...@exemail.com.au wrote:
Suggestions?
quick-fix / hack wise -
probably setup some job to run way more often
that checks the status makes a determination -
or move the job to something like anacron, etc
although, in a laptop situation - you might want
to manage this manually -
On Mon, Oct 18, 2010 at 4:06 PM, Chris Turner
c.tur...@199technologies.org wrote:
elekktrett...@exemail.com.au wrote:
Suggestions?
quick-fix / hack wise -
probably setup some job to run way more often
that checks the status makes a determination -
or move the job to something like
Samuel J. Greear wrote:
That said, I think it would be fine to commit one or more optional
stopgap measures/scripts to the RC system, for mobile users and etc.,
as long as it is well documented that they may go away if a better
solution is developed or derived.
not to flamebait or something -
On Mon, Oct 18, 2010 at 4:39 PM, Chris Turner
c.tur...@199technologies.org wrote:
Samuel J. Greear wrote:
That said, I think it would be fine to commit one or more optional
stopgap measures/scripts to the RC system, for mobile users and etc.,
as long as it is well documented that they may go
What about hammerd?
* Starts when system starts
* Wakes up every 10 seconds or so to check current system load/memory
usage to estimate if its appropriate to run a cleanup operation at this
time.
* Can have a text file configuration where you can specify maximum
size(GB) of history per PFS or %
I think we definitely must have hammer cleanup not depending on periodic.
Especially laptop/workstation users, since they may be running only couple
of hours a day.
The system should be able to automatically initiate hammer cleanup
whenever it's been more than 1 day/x hours since last time it was
10 matches
Mail list logo
