5,838
edits
Category:Cumulus MX: Difference between revisions
m
→Setting up for either manual or automatic running
m (→MXDiags: added missing if) |
|||
| Line 237: | Line 237: | ||
# OR declare a task in the scheduler to start MX; in the '''Actions''' tab fill in fields as follows (the other tabs should be obvious): | # OR declare a task in the scheduler to start MX; in the '''Actions''' tab fill in fields as follows (the other tabs should be obvious): | ||
#**'''Action''' <tt>Start a program</tt> from drop-down | #**'''Action''' <tt>Start a program</tt> from drop-down | ||
#**'''Program/script''' <tt>cmd.exe</tt> | #**'''Program/script''' <tt>cmd.exe</tt> (this is standard Windows environment to run something) | ||
#**'''Add arguments''' <tt>/C start "Start_MX | #**'''Add arguments''' <tt>/C start "Start_MX" \CumulusMX\CumulusMX.exe -debug -port=nnnn</tt> (the "/C" means this task will close once it has started the task, the "Start_MX" is how the task will be labelled as it is running, the next argument actually starts the executable and it does not need a drive prefix as that is in next box. | ||
#** | #**Note in this example I have included two optional parameters that can be used after the .exe call in that same box, here '''-debug''' (only include if you want full debugging logging) and '''port=nnnn''' where nnnn is the port to be used for admin interface (only include if want to change from default 8998), all optional parameters are listed later | ||
#**'''Start in''' <tt>\CumulusMX</tt> (include a drive specifier if necessary) | #**'''Start in''' <tt>\CumulusMX</tt> (include a drive specifier if necessary) | ||