Leo wrote: > have you got cygwin? (www.cygwin.com) I've found that its bash, OpenSSH > and cvs packages are well worth the download; they seem rather more > stable.
I haven't, I will, thanks. > Note that problems with SF may well be because of the SF cvs > install. Trust me, I know, it's been a pain for months. :( > the 1.4.0 sun jdk seems to be rather buggy. Getting the very latest > avoids you some issues. Still, the javadoc tool is known to eat massive > amounts of memory if the codebase is big. Its best to 'nice' the command. Yup, good idea, I'll try that. > > Could it be trying to get keyboard input or something? > > that'd be weird; a process waiting for input usually doesn't draw a 100% > memory. I've had cases where javadoc is chewing 100% CPU and some cased where it is split 50:50 between a java and javadoc. I tried an strace and the java was spinning doing a poll, and the javadoc wasn't registering any system calls -- not even grabbing memory. I coudln't figure out much from that. regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
