jason/socktop-webterm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

remove known issues page
Build and Deploy to K3s / test (push) Failing after 15m2s
Details
Build and Deploy to K3s / lint (push) Has been skipped
Details
Build and Deploy to K3s / build-and-push (push) Has been skipped
Details
Build and Deploy to K3s / deploy (push) Has been cancelled
Details

Browse Source
This commit is contained in:
jasonwitty
2026-08-23 23:26:28 -07:00
parent 74726441c6
commit dc7b51453e
2 changed files with 0 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/src/SUMMARY.md
-2
View File
@@ -26,5 +26,3 @@
- [Monitor Multiple Hosts with Zellij](./advanced/zellij.md) - [Monitor Multiple Hosts with Zellij](./advanced/zellij.md)
- [Agent Direct Integration](./advanced/agent-integration.md) - [Agent Direct Integration](./advanced/agent-integration.md)
- [Socktop Connector Library](./advanced/connector.md) - [Socktop Connector Library](./advanced/connector.md)
[Known Issues](./known-issues.md)
docs/src/known-issues.md
-15
View File
@@ -1,15 +0,0 @@
# Known Issues
Current limitations worth knowing about. See the [issue tracker](https://github.com/jasonwitty/socktop/issues) for the live list.
## Process kill inside containers
The kill feature only offers itself when the agent is local (see [Killing a Process](./usage/general.md#killing-a-process)). A client running inside a container with **host networking but its own PID namespace** can pass that local-agent check even though its PID view differs from the host's. The PID-reuse guard (the process name must still match at signal time) limits the blast radius, but avoid using the kill feature from inside such containers.
## Switching between agents of different versions mid-session
When socktop detects an old agent without the per-process endpoints, it remembers that the details view is unsupported. If you then reconnect the same session to a *different, older* agent, that detection may not reset correctly. Restart socktop when hopping between agents that are generations apart.
## Zellij plugin example
The in-repo `zellij_socktop_plugin` example does not currently compile and is pending a rework. This does not affect [monitoring multiple hosts with Zellij](./advanced/zellij.md), which just runs the normal client in panes.