Dan Nicholson wrote:
On 6/28/06, M.Canales.es <[EMAIL PROTECTED]> wrote:
El Lunes, 26 de Junio de 2006 15:35, Dan Nicholson escribió:
> Attached is one solution that is working on my box (so far). The
> whole system is noticeably less sluggish while building. `top' looks
> normal again.
That have a big bug: if the build of some target fails (or you press
Control-C), progress-bar.sh will loop for ever in the background.
That's why I added "rm -f /tmp/jhalfs.*" to the traps in master.sh.
Would that not work?
ah.. the big question. Are the error routines defined in 'master.sh'
inherited by 'make' and then passed to the spawned script
'progress_bar.sh'. --Don't think so.
Master.sh routines are definitely not available when 'make' is
executed manually.
I will see if we can do the exit tests each second instead of each 120
milliseconds, But that could need a "sleep 1.2" instead current "sleep
.25"
It just has to be a different test than running fuser. It
considerably slowed down my build. With jhalfs, 1 SBU = 19m. Without
jhalfs, 1 SBU = 10m. gcc took forever.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
