Difference between revisions of "socket Interface"
Jump to navigation
Jump to search
m |
m |
||
| Line 3: | Line 3: | ||
You need a separate logs directory for each OpenKore instance which you want to run with Socket interface. | You need a separate logs directory for each OpenKore instance which you want to run with Socket interface. | ||
| − | + | Connect to running OpenKore with Socket interface: | |
| − | |||
| − | + | <tt>src/Interface/attach-to-console.pl <logs>/console.socket --control=<control></tt> | |
| − | |||
Use ctrl+c to close Socket interface client and preserve OpenKore. | Use ctrl+c to close Socket interface client and preserve OpenKore. | ||
Revision as of 06:02, 20 February 2010
Socket interface lacks standard input (such as commands), but can be connected with thin client to handle input and output. Best used to run OpenKores in background and still be able to control them.
You need a separate logs directory for each OpenKore instance which you want to run with Socket interface.
Connect to running OpenKore with Socket interface:
src/Interface/attach-to-console.pl <logs>/console.socket --control=<control>
Use ctrl+c to close Socket interface client and preserve OpenKore.
Use console command 'quit' to shut down OpenKore.
Special instructions, which only apply to Socket interface, can be given in some cases such as errors.
