root@173:/core/sys# boot sequence init...
[ OK ] mounted /dev/173 on /unit/173 (rw,relatime)
starting service "daemon-173.service" ... done
WARN: latency spike on channel CH-173A (4.2ms)
sync[173]: checksum a1:b2:17:3f OK
173@node:~/cluster173$ make build-173
> compiling core173.c ...
> linking → build/173 (ver_1.7.3)
root@173:/core/sys# ./run --profile 173/NEON --mode ACTIVE
[ OK ] profile 173/NEON applied
root@173:/core/sys# hash 173:d4f7 --verify
signature: 173∞ valid=true
channel CH-173X synced @173Hz
173@unit:/opt/173$ cat status.json
{ "id":"173.482", "state":"STABLE", "uptime":"24h" }
root@173:/core/sys# ./sync --target 1-7-3 --force
NOTE: override accepted [1][7][3]
----------------------------------------------------
root@173:/cluster/main# uptime
173 days, load avg: 1.7 1.3 0.73
root@173:/cluster/main# tail -f core173.log
[173] heartbeat OK
[173] heartbeat OK
[173] heartbeat OK
listening on port :17300
root@173:/core/sys# boot sequence init...
[ OK ] mounted /dev/173 on /unit/173 (rw,relatime)
starting service "daemon-173.service" ... done
WARN: latency spike on channel CH-173A (4.2ms)
sync[173]: checksum a1:b2:17:3f OK
173@node:~/cluster173$ make build-173
> compiling core173.c ...
> linking → build/173 (ver_1.7.3)
root@173:/core/sys# ./run --profile 173/NEON --mode ACTIVE
[ OK ] profile 173/NEON applied
root@173:/core/sys# hash 173:d4f7 --verify
signature: 173∞ valid=true
channel CH-173X synced @173Hz
173@unit:/opt/173$ cat status.json
{ "id":"173.482", "state":"STABLE", "uptime":"24h" }
root@173:/core/sys# ./sync --target 1-7-3 --force
NOTE: override accepted [1][7][3]
----------------------------------------------------
root@173:/cluster/main# uptime
173 days, load avg: 1.7 1.3 0.73
root@173:/cluster/main# tail -f core173.log
[173] heartbeat OK
[173] heartbeat OK
[173] heartbeat OK
listening on port :17300