rsday, November 06, 2014 10:40 AM
To: TeraScript-Talk@terascript.com
Subject: RE: TeraScript-Talk: Could not execute fork error
I thought I'd chip in with my suggestion...
Convert your external actions to file writing actions.
Use the files you write out as triggers - have a scheduled
2:15 AM
To: TeraScript-Talk@terascript.com
Subject: RE: TeraScript-Talk: Could not execute fork error
Simply put, yes. This is an error when an External Action is used. They are
poorly written in Witango and you would be good to remove those actions. In my
opinion they are a cause for a majority of stabil
-Talk@terascript.com
Subject: RE: TeraScript-Talk: Could not execute fork error
Simply put, yes. This is an error when an External Action is used. They are
poorly written in Witango and you would be good to remove those actions. In my
opinion they are a cause for a majority of stability issues. They are
Subject: RE: TeraScript-Talk: Could not execute fork error
Simply put, yes. This is an error when an External Action is used. They are
poorly written in Witango and you would be good to remove those actions. In my
opinion they are a cause for a majority of stability issues. They are also very
Simply put, yes. This is an error when an External Action is used. They are
poorly written in Witango and you would be good to remove those actions. In my
opinion they are a cause for a majority of stability issues. They are also very
difficult to debug. What's happened is that the last time one
