Problem
Running sys log <unit> starts a long-lived journalctl -f -u <unit> process. Some services, including hl-visor, inspect process command lines during startup/restart and treat any process whose argv contains the service binary/unit keyword as a matching process.
When sys log hl-visor is active, hl-visor restart can fail with:
more than one matching proc found for keywords matching_procs={..., Pid(...): "journalctl --user -o cat -f -u hl-visor ..."} binary_name=hl-visor
Stopping sys log removes the extra journalctl ... -u hl-visor process and restart succeeds.
Expected
A long-running sys log <unit> follower should not expose <unit> in its persistent process argv, so services that inspect process command lines are not affected by log observation.
Notes
The underlying service-side process matching is broad, but sys-cli can avoid contributing a persistent false-positive argv match for its own log follower.
Problem
Running
sys log <unit>starts a long-livedjournalctl -f -u <unit>process. Some services, includinghl-visor, inspect process command lines during startup/restart and treat any process whose argv contains the service binary/unit keyword as a matching process.When
sys log hl-visoris active,hl-visorrestart can fail with:Stopping
sys logremoves the extrajournalctl ... -u hl-visorprocess and restart succeeds.Expected
A long-running
sys log <unit>follower should not expose<unit>in its persistent process argv, so services that inspect process command lines are not affected by log observation.Notes
The underlying service-side process matching is broad, but sys-cli can avoid contributing a persistent false-positive argv match for its own log follower.