Difference between revisions of "socket Interface"
Jump to navigation
Jump to search
(Created page with '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 …') |
m |
||
| Line 14: | Line 14: | ||
Special instructions, which only apply to Socket interface, can be given in some cases such as errors. | Special instructions, which only apply to Socket interface, can be given in some cases such as errors. | ||
| + | |||
| + | [[Category:Interfaces]] | ||
Revision as of 17:01, 5 November 2009
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.
Run OpenKore with Socket interface:
- openkore.pl --control=<control> --logs=<logs> --interface=Socket
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.
