Forum OpenACS Q&A: Re: Is it possible to use the native exec command while also using nsproxy?

Collapse
6: Re: Is it possible to use the native exec command while also using nsproxy? (response to 5)
Posted by Gustaf Neumann on 11/01/13 11:15 PM
i was not suggesting to replace the perl stuff by tcl. In case you have a quick loop with many execs of the form 
   while {...} {
      set x [exec perl script.pl]
   }
it would be better to make yet another script containing the loop + call of the perl script, and call this additional script via a single exec.
Collapse
7: Re: Is it possible to use the native exec command while also using nsproxy? (response to 6)
Posted by Colin Charbonneau on 11/04/13 09:30 PM
I see what you mean.

I'm not sure if that is possible in this case. After the perl script returns, it outputs a string containing a file path and then is passed to a different proc. If my perl script never returns, I can never pass it back to the tcl?

I'm left wondering about the nature of the deadlock error within proxy::exec. Is it some sort of timing issue that can be solved with a sleep command? If you have any information on how this happens, that would be greatly appreciated.

Collapse
8: Re: Is it possible to use the native exec command while also using nsproxy? (response to 7)
Posted by Gustaf Neumann on 11/05/13 03:30 PM
i have never seen proxy::exec leading to a deadlock. How are you handling the situation when the perl script never returns? ns_proxy (the machinery used by proxy::exec) has several timeouts [1]. Can it be that your server is running out of slaves? Are you using AOLserver or NaviServer?

-gn
[1] http://naviserver.sourceforge.net/n/nsproxy/files/ns_proxy.html