Parents (Total: 8)

The searched file hash is included in 8 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
FileSize	29596
MD5	9438942DB52AE96850E25C2E412FC2C9
PackageDescription	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. . 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. . 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.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	conmon
PackageSection	admin
PackageVersion	2.0.20-1
SHA-1	AB558C09E1D01A279C8FB0BE544C072C75C214DF
SHA-256	C6C73A21DBA0ED3AEB748E63424623F354E4483C1233B2704BE4FE5401C023DE

Key	Value
FileSize	26800
MD5	229ECD9E134BFAF0C744E764C617F488
PackageDescription	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. . 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. . 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.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	conmon
PackageSection	admin
PackageVersion	2.0.9-1
SHA-1	45DAC8B72E88FB5BC6687AB0357950EF3916EFE0
SHA-256	C43CD1BD8C70BEEF4C609D610D304285201C4CB5574ABF74D964A55FEBB4F960

Key	Value
FileSize	22820
MD5	008F0C0C693475E73312A269D2F09A84
PackageDescription	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. . 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. . 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.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	conmon
PackageSection	admin
PackageVersion	2.0.0-1
SHA-1	D791FC1B6E9872D46247F021710A1B85B509CDEF
SHA-256	F19D746B967A53E3557C6F372753FCF6E116429DCB6E29FD9EE71A4F9F5A198F

Key	Value
FileSize	24688
MD5	3073BAA9F1C433C53190AD4877E6BB30
PackageDescription	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. . 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. . 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.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	conmon
PackageSection	admin
PackageVersion	2.0.0-1
SHA-1	44369071AB2914BA752B12F7BDBFB2594A19F9A4
SHA-256	9B500567862C82E92266B7207A411655830909E9AF59070B4C3356FA6573E5D8

Key	Value
FileSize	24468
MD5	7CF977A0114CE7B5A8B299C51357593A
PackageDescription	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. . 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. . 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.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	conmon
PackageSection	admin
PackageVersion	2.0.0-1
SHA-1	A599165D5005F04EC3C6CD691260D881FFD11F79
SHA-256	BC064EDDBAD1B39EE2197070BC9A27A15CFACB003C843A4B7D13F94B59A3A1ED

Key	Value
FileSize	22744
MD5	6786A84BC8EA73A8CAF05A00B8351CE9
PackageDescription	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. . 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. . 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.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	conmon
PackageSection	admin
PackageVersion	2.0.0-1
SHA-1	731795167C779DEF554E3502CDC42989B4BCEB23
SHA-256	F3412AE5F5407E2E69A5624FF8A71944CD8B03586D49784ED7D191F339A239D3

Key	Value
FileSize	23216
MD5	81E48F6B4CAA2B258E6E27335CC010E1
PackageDescription	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. . 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. . 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.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	conmon
PackageSection	admin
PackageVersion	2.0.0-1
SHA-1	209A87485A6A26A9C5E172AA07EFB42C911C1485
SHA-256	11560E4779535D4939BFCB1C25494B4EA22EF9F98584015196592DA5DD30F27D

Key	Value
FileSize	26192
MD5	3A4C42675A4B03353AB67864BBC7490F
PackageDescription	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. . 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. . 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.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	conmon
PackageSection	admin
PackageVersion	2.0.0-1
SHA-1	3AE9717FE1209781FCE1151D1AECD5AEEA862B74
SHA-256	0A572F8DD59B3159A9ACE428E0767D4C3B70A0580E18984FA78CA4077E9DA84F