Parents (Total: 6)

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

Key	Value
FileSize	36240
MD5	D8E3BEE1F3F3BFB87C96AD9F93CE4D31
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	Podman Packaging Team <team+podman@tracker.debian.org>
PackageName	conmon
PackageSection	admin
PackageVersion	2.1.6+ds1-1
SHA-1	08E0F7D076705CB23A424AC262F122F218A7AB5F
SHA-256	2654F01B8E190A50F0CE0FEFFB0B660560D20D22CBC73505E4FCB82E3B11E8AA

Key	Value
FileSize	36048
MD5	AA57B5960BAD4E4D29C8DCCACDEB30FD
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	Podman Packaging Team <team+podman@tracker.debian.org>
PackageName	conmon
PackageSection	admin
PackageVersion	2.1.6+ds1-1
SHA-1	BBE8F1BAC2C9758CC5FC0E7956234AB5E88F93C0
SHA-256	9D15CAB56DC01B228C6D889B8159C1A45EB995C5938CBC9467BC19E01F36E3E7

Key	Value
FileSize	35540
MD5	6CE9A975AC6C825AAD60BA275A824C5E
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	Podman Packaging Team <team+podman@tracker.debian.org>
PackageName	conmon
PackageSection	admin
PackageVersion	2.1.6+ds1-1
SHA-1	96FA12617BAC333C24560538A381D40238837345
SHA-256	F05DDC519342017D85C546E3331A5380B6CCC7F99E273CD3D2628A14666470CF

Key	Value
FileSize	38328
MD5	698CF15E28F54CFF13C9C91269D796E7
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	Podman Packaging Team <team+podman@tracker.debian.org>
PackageName	conmon
PackageSection	admin
PackageVersion	2.1.6+ds1-1
SHA-1	C0E5CCA79A1BF966101B22BAA539D42DD82CCD3F
SHA-256	3C882ECE1E1AD0887E6A8E336F38173B3E3917CC03AF6EBAD447CF66D8BA15EF

Key	Value
FileSize	37932
MD5	40E7E1B81979E3EE248775739422ADFE
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	Podman Packaging Team <team+podman@tracker.debian.org>
PackageName	conmon
PackageSection	admin
PackageVersion	2.1.6+ds1-1
SHA-1	A77EAAC644FDDE745168BEE75452C445D3AE8C43
SHA-256	2D4111853199DD8C7CBCDA3DA04F37D9B7F3A7B08DC1CEE546A1E5518DE8A596

Key	Value
FileSize	10900
MD5	F8A29D5065C201FE90D9219B3DA90B41
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. . This package contains golang sources that other packages may require for building.
PackageMaintainer	Podman Packaging Team <team+podman@tracker.debian.org>
PackageName	golang-github-containers-conmon-dev
PackageSection	admin
PackageVersion	2.1.6+ds1-1
SHA-1	69354A08E264205BEE876D10E57BEEBA4D400ECB
SHA-256	4A51221BEA036184FFB2C39E1A0B03CB1E050D06B9042B3C324C090C8C574A16