salt/mc-scripts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

More fixes

Browse Source
This commit is contained in:
Salt 2024-02-16 23:41:22 -06:00
parent ba57f4a7ae
commit bee8f740c6
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
storage-net/README.md
View File

@ -50,8 +50,8 @@ Packet format is uniform between master <-> slaves and is structured like so:
* The slave starts up * The slave starts up
* The slave receives a `ping` packet from a master server. The slave compares it to any stored `/pairednetwork` file in the root of the filesystem: * The slave receives a `ping` packet from a master server. The slave compares it to any stored `/pairednetwork` file in the root of the filesystem:
* If the file exists and the ID does not match, processing is halted * If the file exists and the ID does not match, processing is halted
* The `networkid` of the packet is stored as `/pairednetwork` * The `networkid` of the packet is stored as `/pairednetwork`
* The slave responds with a `pong` packet. * The slave responds with a `pong` packet.
### Master Node Initialization ### Master Node Initialization
@ -67,7 +67,7 @@ Packet format is uniform between master <-> slaves and is structured like so:
* All available slaves respond with `pong` * All available slaves respond with `pong`
* The sender node sends a packet with type `query`. Field `itemname` is populated with an item to query for. * The sender node sends a packet with type `query`. Field `itemname` is populated with an item to query for.
* Each available slave responds with type `query`. * Each available slave responds with type `query`.
* `itemname` is populated with data from the previous packet * `itemname` is populated with data from the previous packet
* `itemquantity` is populated with the quantity of that item attached to storages the slave has access to. * `itemquantity` is populated with the quantity of that item attached to storages the slave has access to.
* The requester waits for a response from each slave that responded to the `ping` or until a configurable timeout is reached. * The requester waits for a response from each slave that responded to the `ping` or until a configurable timeout is reached.
* Results are consumed * Results are consumed