Why does cnet terminate after 5 minutes?
Errors in your protocols which prevent an event handler from returning when expected, prevent the cnet scheduler from performing correctly. In particular, the scheduler cannot service events from the windowing system – for example your requests to kill cnet itself when you detect a problem. To overcome this major problem, cnet itself times-out after 5 minutes just in case you have written incorrect protocols which have become ‘stuck’. Once you are confident that your protocols are working as expected you can easily extend this 5 minute period with, for example, cnet -m 10 TOPOLOGY where the command line option requests execution for the required number of minutes.
