Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support detached console #8

Closed
rsmmr opened this issue Feb 10, 2022 · 0 comments
Closed

Support detached console #8

rsmmr opened this issue Feb 10, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@rsmmr
Copy link
Member

rsmmr commented Feb 10, 2022

That would allow attaching a console to an already running agent.
@rsmmr rsmmr added the enhancement New feature or request label Feb 10, 2022
rsmmr added a commit that referenced this issue Feb 24, 2023
@rsmmr
[WIP] Support attaching interactive console to running agent.
0cd5f85 
Closes #8.
rsmmr added a commit that referenced this issue Feb 27, 2023
@rsmmr
Support attaching interactive console to running agent.
594b5ee 
Closes #8.
rsmmr added a commit that referenced this issue Jan 4, 2024
@rsmmr
Support attaching interactive console to a running agent.
dec4179 
By default, an agent now creates a UNIX socket for its console that an
external client can connect to. To connect to an already running
agent, execute `zeek-agent -r` on the same machine (note that client
and server must be running as the same user, probably `root`). Client
and server can specify a different socket path through `-s <PATH>`.
The environment variable `ZEEK_AGENT_SOCKET` can be set to specify the
path as well.

Remote consoles aren't support on Windows yet.

Internally, we switch the classic local console over to the same IPC
mechanism we now use for remote consoles, so that there's only one
implementation. For Windows, where actual IPC isn't implemented yet,
we provide a dummy implementation for this purpose that just forwards
data inside the main (and only) process.

Closes #8.
rsmmr added a commit that referenced this issue Jan 4, 2024
@rsmmr
Support attaching interactive console to a running agent.
f05d801 
By default, an agent now creates a UNIX socket for its console that an
external client can connect to. To connect to an already running
agent, execute `zeek-agent -r` on the same machine (note that client
and server must be running as the same user, probably `root`). Client
and server can specify a different socket path through `-s <PATH>`.
The environment variable `ZEEK_AGENT_SOCKET` can be set to specify the
path as well.

Remote consoles aren't support on Windows yet.

Internally, we switch the classic local console over to the same IPC
mechanism we now use for remote consoles, so that there's only one
implementation. For Windows, where actual IPC isn't implemented yet,
we provide a dummy implementation for this purpose that just forwards
data inside the main (and only) process.

Closes #8.
@rsmmr rsmmr closed this as completed in f8a284d Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rsmmr