On 10 October 2011 21:40, John Kasunich <jmkasun...@fastmail.fm> wrote: > I'm a little surprised that the halmeter tracked the change > from 40 to 300. I would have expected the halmeter to continue > watching the memory associated with the signal, even after the > signal was deleted (another glimpse behind the curtain). Did > you use one instance of halmeter the whole time, or did you > start halmeter, observe the reading, then stop it and issue > another hal command?
Just one Halmeter, open all the time. Thanks for the explanation, that's a lot more benign than I feared. -- atp "Torque wrenches are for the obedience of fools and the guidance of wise men" ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
