On 09/22/2011 06:46 PM, Daniel Carbajo wrote:
> Mmmmm, I've never experienced that... what can make a script fail and how
> would be the message? Do you have any example?
>
Actually you did experience that but might have not been aware of it.
See this example error message I posted in an earlier email in this thread:
eval ERROR: unexpected end of script command
----
e_x_p_r_e_s_s_i_o_n = catom . >> label <<
Error evaluating: catom.label
unexpected end of script command
----
e_x_p_r_e_s_s_i_o_n = catom . >> label <<
This is an "expected" case where the command parser provided an error
message. But there are also "unexpected" cases possible where you get an
"EXCEPTION" message or no message at all.
Therefore I think it will be dangerous to try to count commands by using
these messages to achieve your goal.
Regards,
Rolf
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
