diff options
| author | B. Watson <yalhcru@gmail.com> | 2022-03-14 12:05:27 -0400 |
|---|---|---|
| committer | B. Watson <yalhcru@gmail.com> | 2022-03-17 12:38:04 -0400 |
| commit | 17a6f8fb9c0827e97e6dbf6ddf6e8ece588db940 (patch) | |
| tree | 345f8a52fc3ec971b6e15082134e1eb55f023275 /system/conmon | |
| parent | db0217a3042c9fdd8d712b872355319db2997e1d (diff) | |
system/conmon: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'system/conmon')
| -rw-r--r-- | system/conmon/README | 33 |
1 files changed, 17 insertions, 16 deletions
diff --git a/system/conmon/README b/system/conmon/README index 8c1e2691b9b6..8aec03abe198 100644 --- a/system/conmon/README +++ b/system/conmon/README @@ -1,24 +1,25 @@ An OCI container runtime monitor. -Conmon is a monitoring program and communication tool between a container -manager (like podman or CRI-O) and an OCI runtime (like runc or crun) for a -single container. +Conmon is a monitoring program and communication tool between a +container manager (like podman or CRI-O) and an OCI runtime (like runc +or crun) for a single container. -Upon being launched, it double-forks to daemonize and detach from the parent -that launched it. It then launches the runtime as its child. This allows -managing processes to die in the foreground, but still be able to watch over -and connect to the child process (the container). +Upon being launched, it double-forks to daemonize and detach from +the parent that launched it. It then launches the runtime as its +child. This allows managing processes to die in the foreground, but +still be able to watch over and connect to the child process (the +container). While the container runs, conmon does two things: - Provides a socket for attaching to the container, holding open the - container's standard streams and forwarding them over the socket. Writes - the contents of the container's streams to a log file (or to the systemd - journal) so they can be read after the container's death. +- Provides a socket for attaching to the container, holding open the + container's standard streams and forwarding them over the socket. +- Writes the contents of the container's streams to a log file (or to + the systemd journal) so they can be read after the container's death. -Finally, upon the containers death, conmon will record its exit time and code -to be read by the managing programs. +Finally, upon the containers death, conmon will record its exit time +and code to be read by the managing programs. -Written in C and designed to have a low memory footprint, conmon is intended -to be run by a container managing library. Essentially, conmon is the smallest -daemon a container can have. +Written in C and designed to have a low memory footprint, conmon +is intended to be run by a container managing library. Essentially, +conmon is the smallest daemon a container can have. |