<?xml version="1.0" encoding="windows-1252"?>
<node id="1022102" title="Re^5: Program Design Around Threads" created="2013-03-06 17:03:48" updated="2013-03-06 17:03:48">
<type id="11">
note</type>
<author id="171588">
BrowserUk</author>
<data>
<field name="doctext">
&lt;blockquote&gt;&lt;i&gt;There are as many threads running as there are machines and commands&lt;/i&gt;&lt;/blockquote&gt;

&lt;p&gt;Only if you run the different commands for each machine from different threads. That's the wrong way to do it.

&lt;p&gt;If you look at the code snippets I posted, one thread connect to one machine, opens one file, and &lt;i&gt;runs all the commands for that machine&lt;/i&gt;, &lt;b&gt;sequentially&lt;/b&gt;. That way, there is no possibility for ordering problems or file conflicts.

&lt;blockquote&gt;&lt;i&gt;Maybe I am missing something?&lt;/i&gt;&lt;/blockquote&gt;

&lt;p&gt;Please read my last post slowly and thoroughly. Making multiple connections to each machine from different threads to run single commands is both inefficient and the source of your problems.


&lt;div class="pmsig"&gt;&lt;div class="pmsig-171588"&gt;
&lt;hr /&gt;
&lt;font size=1 &gt;
&lt;div&gt;With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'&lt;/div&gt;
&lt;div&gt;Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.&lt;/div&gt;
&lt;div&gt;"Science is about questioning the status quo. Questioning authority". &lt;/div&gt;
&lt;div&gt;In the absence of evidence, opinion is indistinguishable from prejudice.
&lt;/div&gt;
&lt;/font&gt;

&lt;/div&gt;&lt;/div&gt;</field>
<field name="root_node">
1021943</field>
<field name="parent_node">
1022094</field>
</data>
</node>
