fix(svos-apps): svos-terminal unit reaches zellij (~/.cargo/bin on PATH); app-terminal up after 2 days degraded
A user unit's default PATH lacks ~/.cargo/bin, so every zellij call from app-terminal failed to launch (rc 127 under the unit's environment), and the app reported degraded from the U13 cutover on. With PATH set, the kernel logged app-terminal up at 15:56:40Z; the pinned manifest is unchanged and no card was raised.
This commit is contained in:
@@ -16,6 +16,9 @@ EnvironmentFile=/etc/svos/env/terminal.env
|
|||||||
Environment=SVOS_KERNEL_URL=https://svos-kernel.phasefinal.com
|
Environment=SVOS_KERNEL_URL=https://svos-kernel.phasefinal.com
|
||||||
Environment=SVOS_DATA_ROOT=/var/lib/svos
|
Environment=SVOS_DATA_ROOT=/var/lib/svos
|
||||||
Environment=SVOS_APP_LISTEN=127.0.0.1:8404
|
Environment=SVOS_APP_LISTEN=127.0.0.1:8404
|
||||||
|
# zellij is lkraven's cargo install (~/.cargo/bin), which a user unit's default PATH does not reach. Without it every
|
||||||
|
# `zellij` call fails to launch: /health stays "degraded" and dump/inject cannot run (found 2026-10-13, svos-dev's report).
|
||||||
|
Environment=PATH=/home/lkraven/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
|
||||||
ExecStart=/opt/svos/current/apps-env/bin/svos-terminal
|
ExecStart=/opt/svos/current/apps-env/bin/svos-terminal
|
||||||
[Install]
|
[Install]
|
||||||
WantedBy=default.target
|
WantedBy=default.target
|
||||||
|
|||||||
Reference in New Issue
Block a user