Re: [Emc-developers] RTAPI threads: motion vs threads

2013-01-26 Thread Gene Heskett
On Saturday 26 January 2013 09:25:57 John Kasunich did opine: Message additions Copyright Saturday 26 January 2013 by Gene Heskett > On Fri, Jan 25, 2013, at 08:06 PM, Michael Haberler wrote: > > In the current code, the only components which start RT threads are > > motion (motmod) and threads th

Re: [Emc-developers] RTAPI threads: motion vs threads

2013-01-25 Thread John Kasunich
On Fri, Jan 25, 2013, at 08:06 PM, Michael Haberler wrote: > In the current code, the only components which start RT threads are motion > (motmod) and threads > the only components which stop threads are hal_lib and motmod > > they differ as follows: > > - unloading 'motmod' stops all threads

Re: [Emc-developers] RTAPI threads: motion vs threads

2013-01-25 Thread Michael Haberler
Am 26.01.2013 um 02:21 schrieb andy pugh: > On 26 January 2013 01:06, Michael Haberler wrote: > >> I know barely anybody uses the threads module so that's likely safe but I'm >> raising it more to clarify semantics than to cry wolf. > > I use it very often (dozens of invocations a day), howev

Re: [Emc-developers] RTAPI threads: motion vs threads

2013-01-25 Thread andy pugh
On 26 January 2013 01:06, Michael Haberler wrote: > I know barely anybody uses the threads module so that's likely safe but I'm > raising it more to clarify semantics than to cry wolf. I use it very often (dozens of invocations a day), however I would expect the threads to stop if I unloaded it

[Emc-developers] RTAPI threads: motion vs threads

2013-01-25 Thread Michael Haberler
In the current code, the only components which start RT threads are motion (motmod) and threads the only components which stop threads are hal_lib and motmod they differ as follows: - unloading 'motmod' stops all threads - unloading 'hal_lib' stops all threads - unloading 'threads' does _not_ st