Skip to content

fix(coder-workspace-status): name programs started through the loader - #10

Merged
matifali merged 1 commit into
mainfrom
atif/coder-workspace-status-loader-name
Nov 2, 2026
Merged

matifali merged 1 commit into
mainfrom
atif/coder-workspace-status-loader-name

Conversation

@matifali

Copy link
Copy Markdown
Member

Follow-up to #9.

A listener started through the dynamic loader showed the loader's name in the status line and card. The portable desktop's VNC server, for example, runs as ld-linux-x86-64.so.2 --library-path DIR .../bin/Xvnc.real, so port 5901 read ld-linux-x86-64.so.2.

proc_label now names such a process after the program the loader runs. It skips the loader's options, and drops a .real suffix, so port 5901 reads Xvnc.

Testing

  • make lint passes; shellcheck and shfmt -i 2 -ci are clean on scripts/coder-status.
  • In a dogfood workspace running the portable desktop, coder-status json reports port 5901 as Xvnc. Other listeners keep their names (node vite.js, python3 http.server, ttyd).

A listener run as ld-linux-x86-64.so.2 --library-path DIR PROGRAM, like the
portable desktop's Xvnc, showed the loader's name. It now shows PROGRAM.
@matifali matifali self-assigned this Oct 29, 2026
@matifali
matifali merged commit 00cb9c2 into main Nov 2, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant