remove known issues page
This commit is contained in:
@@ -26,5 +26,3 @@
|
||||
- [Monitor Multiple Hosts with Zellij](./advanced/zellij.md)
|
||||
- [Agent Direct Integration](./advanced/agent-integration.md)
|
||||
- [Socktop Connector Library](./advanced/connector.md)
|
||||
|
||||
[Known Issues](./known-issues.md)
|
||||
@@ -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.
|
||||
Reference in New Issue
Block a user