Hi, I've been running Gump via cron on my box for quite some time now and since a couple of days one of the first things I have to do when I log in at the morning is killing java - for some reason jakarta-cactus-sample-servlet-12 is hanging in the test target of the spawned process.
Sam, for your builds on nagoya all processes that run for more than 20 minutes get killed (or so it seems) - how have you done that? I'm talking about this, that you can see for all intermediate Gump runs and the dist-ant project for example: > /home/rubys/bin/timeout: timed out > java: died with signal 4 I don't see any traces of it in the generated build.sh, are you patching the one for nagoya? Is this something we could introduce for Gump in general (like a profile wide option)? Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
