As one of the people that got bombarded by this, is there any reason you
aren't using something like Hudson or Jenkins to run your Integration
builds? They have email notification ability built in, and are widely
configurable. Plus you don't need to try and hunt down any special PID
or task if it starts misbehaving, you just kill the job, and the other
builds can still continue.
Dave
On 07/01/2011 12:23 AM, Samisa Abeysinghe wrote:
On Fri, Jul 1, 2011 at 9:41 AM, Supun Malinga <[email protected]
<mailto:[email protected]>> wrote:
Hi Samisa,
On Fri, Jul 1, 2011 at 9:16 AM, Samisa Abeysinghe <[email protected]
<mailto:[email protected]>> wrote:
Is this fixed now? What caused the error?
yes it is. This was due to having a wrong path set in the script.
Script started to run recursively changing pid each time. Took
some time for me to get the process killed. Thats what made all
these mails. :(
Note that there is a pause lock mechanism to terminate the script
rather than killing. Please look for the word "pause" in the script
towards the end of it.
Thanks,
Samisa...
Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
