>>> I always turn off screensaver and all the other little tools like >>> MenuMeters etc that I have running. >> Yes, MenuMeters is running. But I don't know about it. >> >>> I only allow the screen to go to sleep after five minutes. >> Maybe this is correct setting. BTW I don't have a display. Just connetcting >> via VNC :) >> >>>> I have serious breakage with MacOSX OOo 2.3.1 RC1 PPC build >>>> and if I turned off screen saver turned off, now it build is progressing >>>> until NS language. I suspect CPU power is sucked into screen >>>> saver, and sometimes >>>> hdiutil or screensaver eats up all CPU time, then regcomp fails. >>> >>> Is it necessary for you to let hdiutil run while you compile OOo? >> >> No, but while creating packages, dmake runs hdiutil. > >Right. Isn't it diskutil? Anyway one of those two apps is used.
hdutil is used to build the .dmg file. diskutil has a different purpose. > >> Sometimes hdiutil >> doesn't exit and eats up CPU. Then build fails. Still I'm not sure >> the connections between build failure and high CPU occupation. > >There are connections. I experienced the same with my MacMini here >last Wednesday. I was compiling OOo, only en-US, de, fr, but at the >same time the Mac was encoding a movie to mp4 and Azureus was >running. Normally no problem but this time the Mac hit the 100% and >fell asleep. I know that a Mac Mini is more sensitive when it comes >to temperatures than a G5. > The MacMini should be more sensitive than a G5 'in a box' as it is smaller and has less space to disipate heat. However, your builds should not take it to the shutdown temperature. I'm guessing that something else did this. I have not built OpenOffice.org in a long time, but on my PowerBook G4 it took about a day to build four languages and on my MacBook Pro about 6 hours to accomplish the same task. This did not bring either system anywhere near max temp or CPU. James --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
