Seems I was wrong. It only appears as a problem when i am compiling FROM a windows cygwin box. I ran make -j8 (from the linux box) (i only have 3 distcc_hosts) it ran ok.
If i run make -jx from the cygwin box, it doesn't seem to like using localhost as a distcc client.... -darryl > Thus spake darryl: > >> While i dont' have an answer to the question it does remind me to >> point out something that happened to me when specifying more jobs than >> CPU's using Windows 2000 cygwin 'hosts.' The scenario is building on >> linux using Cygwin->linux cross-compilers on 2 windows boxes. >> >> If i specify make -jx where x is more than the actual number of CPU's >> available; the cygwin boxes go crazy... 100% CPU usage by distccd. I >> basically have to kill distccd on the main machine then kill distccd >> on the cygwin boxes to regain control. > > Ah, that means you are not wasting electricity then :) Except for > burning spare cycles running windows. > > 100% CPU, and _crazy_ does not supprise me on windows. Process > management is less than desirable in windows. > _______________________________________________ distcc mailing list [EMAIL PROTECTED] http://lists.samba.org/cgi-bin/mailman/listinfo/distcc
