Show More
| @@ -1298,9 +1298,9 b' class CondorLauncher(BatchSystemLauncher):' | |||||
| 1298 | We use the ip{cluster, engine, controller} scripts as our executable to circumvent |
|
1298 | We use the ip{cluster, engine, controller} scripts as our executable to circumvent | |
| 1299 | this - the mechanism of shebanged scripts means that the python binary will be |
|
1299 | this - the mechanism of shebanged scripts means that the python binary will be | |
| 1300 | launched with argv[0] set to the *location of the ip{cluster, engine, controller} |
|
1300 | launched with argv[0] set to the *location of the ip{cluster, engine, controller} | |
| 1301 | scripts on the remote node*. This means that: |
|
1301 | scripts on the remote node*. This means you need to take care that: | |
| 1302 | a. The default path to ipengine etc scripts on your remote node needs to be |
|
1302 | a. Your remote nodes have their paths configured correctly, with the ipengine and ipcontroller | |
| 1303 | in the same directory as the python executable you wish to run |
|
1303 | of the python environment you wish to execute code in having top precedence. | |
| 1304 | b. This functionality is untested on Windows. |
|
1304 | b. This functionality is untested on Windows. | |
| 1305 |
|
1305 | |||
| 1306 | If you need different behavior, consider making you own template. |
|
1306 | If you need different behavior, consider making you own template. | |
General Comments 0
You need to be logged in to leave comments.
Login now