We use STAF/STAX for testing, so this particular problem is in a STAX test
"server" -> STAF "client" situation.
Occasionally, I get a hung process... what seems to happen is that the
command returns, but for whatever reason, the STAX machine doesn't get the
return. Normally, this wouldn't be too difficult; just put a timer on the
process (for example, we install our product on AIX using installp and it
shouldn't take more than a minute or two at most).
However, it seems that timers do not ... interrupt, I guess, a process?
Quick code example (on-the-fly, not copy/paste from actual XML):
<timer duration="'1m'">
<sequence>
<process name="'cat /etc/filesystems'">
<location>machineIP</location>
<command mode="'shell'">"cat /etc/filesystems"</command>
<stderr mode="'stdout'" />
<returnstdout />
</process>
<log level="'trace'">"Got /etc/filesystems:\n%s" % STAXResult
[0][1]</log>
</sequence>
</timer>
<if expr="RC != 0">
<log level="'error'">"ERROR: trying to cat /etc/filesystems took
longer than 1m!"</log>
</if>
I guess my question is: is it true that a timer cannot interrupt a "hung"
process and force STAX to move on, or am I doing something wrong :)
And if it is true, is that even possible, or should I not open a feature
request.
Thanks!
Paul E.------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
