##// END OF EJS Templates
Work to address the review comments on Fernando's branch....
Work to address the review comments on Fernando's branch. * Added comment about Magic(object) (r1224) * Moved InteractiveTB.set_mode from IPythonApp -> InteractiveShell (r1229) * Moved pylabtools.py to IPython/lib (r1229) * Cleaned up comments and copyrights in testing (r1233) * Added comment about ip.shell._ofind (r1237) * Removed "Bye." from quitter (r1240). * Refactored and removed :mod:`IPython.utils.genutils` and :mod:`IPython.utils.platutils`. These modules have been replaced by topical focused modules in :mod:`IPython.utils`. * Refactored tests in :mod:`IPython.utils.tests`. * Moved :func:`IPython.testing.tools.temp_pyfile` to :mod:`IPython.utils.io`. * Moved :func:`IPython.testing.tools.cmd2argv` to :func:`IPython.testing.tools.pycmd2argv` and documented the fact that this only works with Python based command line programs. * Created a new :func:`IPython.utils.path.get_ipython_module_path` to use in finding paths to IPython modules.

File last commit:

r2099:9d979be0
r2498:3eae1372
Show More
ipcontroller.1
87 lines | 2.0 KiB | application/x-troff | GroffLexer
.TH IPCONTROLLER 1 "October 29, 2008" "" ""
.SH NAME
\fBipcontroller \- IPython parallel computing controller control tool
.SH SYNOPSIS
.nf
.fam C
\fBipengine\fP [\fIoptions\fP]
.fam T
.fi
.SH DESCRIPTION
ipcontroller is a control tool for IPython's parallel computing functions.
.SH OPTIONS
.TP
.B
\-h, \-\-help
show this help message and exit
.TP
.B
\-\-client\-ip=CLIENT_IP
the IP address or hostname the controller will listen on for
client connections
.TP
.B
\-\-client\-port=CLIENT_PORT
the port the controller will listen on for client connections
.TP
.B
\-\-client\-location=CLIENT_LOCATION
hostname or ip for clients to connect to
.TP
.B
\-x
turn off all client security
.TP
.B
\-\-client\-cert\-file=CLIENT_CERT_FILE
file to store the client SSL certificate
.TP
.B
\-\-task\-furl\-file=TASK_FURL_FILE
file to store the FURL for task clients to connect with
.TP
.B
\-\-multiengine\-furl\-file=MULTIENGINE_FURL_FILE
file to store the FURL for multiengine clients to connect with
.TP
.B
\-\-engine\-ip=ENGINE_IP
the IP address or hostname the controller will listen on for engine connections
.TP
.B
\-\-engine\-port=ENGINE_PORT
the port the controller will listen on for engine connections
.TP
.B
\-\-engine\-location=ENGINE_LOCATION
the IP address or hostname for engine to connect to
.TP
.B
\-y
turn off all engine security
.TP
.B
\-\-engine\-cert\-file=ENGINE_CERT_FILE
file to store the engine SSL certificate
.TP
.B
\-\-engine\-furl\-file=ENGINE_FURL_FILE
file to store the FURL for engines to connect with
.TP
.B
\-l LOGFILE, \-\-logfile=LOGFILE
log file name (default is stdout)
.TP
.B
\-r
try to reuse all furl files
.SH SEE ALSO
.BR ipython(1), ipcluster(1), ipengine(1)
.br
.SH AUTHOR
\fBipcontroller\fP is a tool that ships with IPython, created by
the IPython Development Team.
.PP
This manual page was written by Stephan Peijnik <debian@sp.or.at>,
for the Debian project (but may be used by others). Modified by Fernando Perez
<Fernando.Perez@berkeley.edu> for inclusion in IPython.