mirror of
https://github.com/jlu5/PyLink.git
synced 2024-11-24 03:29:28 +01:00
relay-quickstart: clarify the problem of duplicate network links some more
[skip ci]
This commit is contained in:
parent
584b7e3712
commit
2246aea13c
@ -26,7 +26,7 @@ While PyLink is generally able to run independently of individual networks's ser
|
|||||||
- Multiple PyLink Relay instances:
|
- Multiple PyLink Relay instances:
|
||||||
- **Do NOT connect a network twice to any PyLink instance**.
|
- **Do NOT connect a network twice to any PyLink instance**.
|
||||||
- **Do NOT connect a network to 2+ separate PyLink instances if there is another network already acting as a hub for them**.
|
- **Do NOT connect a network to 2+ separate PyLink instances if there is another network already acting as a hub for them**.
|
||||||
- Not following these rules means that it's very easy for the Relay instances to go in a loop, whcih will hammer your CPU and seriously spam your channels.
|
- Not following these rules means that it's very easy for the Relay instances to go in a loop should an operator run the wrong command, which will hammer your CPU and relentlessly spam your channels.
|
||||||
|
|
||||||
## Relay commands
|
## Relay commands
|
||||||
The concept of relay channels in PyLink is greatly inspired by Janus, though with a few differences in command syntax.
|
The concept of relay channels in PyLink is greatly inspired by Janus, though with a few differences in command syntax.
|
||||||
|
Loading…
Reference in New Issue
Block a user