Result for 27529F5B014B5A551EBA5112FEE9F6A75970954D

Query result

Key Value
FileName./usr/share/doc/conmon/changelog.Debian.gz
FileSize945
MD56A0F047953647F811E4BAFD84C32C44A
SHA-127529F5B014B5A551EBA5112FEE9F6A75970954D
SHA-2560AD243D4960E4095F850BEE013A932E8B9B6A03CBF45E917696CC538BCDBEE62
SSDEEP24:XCMEGFTFUKBZ+8lbIrZsocCVYo7qt8cgz7e:XSGFTFb+8lb2ZsocV0qt8F7e
TLSHT171119853582BD9BCCED6017B365931911F597343A1E8BB0E34006765528D040E4CDF4E
hashlookup:parent-total9
hashlookup:trust95

Network graph view

Parents (Total: 9)

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

Key Value
FileSize31928
MD52033D6D2E104650E970F3F7A1918E37B
PackageDescriptionOCI 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.
PackageMaintainerPodman Packaging Team <team+podman@tracker.debian.org>
PackageNameconmon
PackageSectionadmin
PackageVersion2.0.25+ds1-1.1
SHA-1CED24628403F70920C27036FD623A5F45EDDD1AB
SHA-2560BD606336E333BBB9FFD376560A7EB2D3A844E204EA0CA739E956FCFC01D932D
Key Value
FileSize34368
MD54B623F7ECC0FD0830C826A17C05F3232
PackageDescriptionOCI 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.
PackageMaintainerPodman Packaging Team <team+podman@tracker.debian.org>
PackageNameconmon
PackageSectionadmin
PackageVersion2.0.25+ds1-1.1
SHA-178A2BE642AF753BCC58E659635A035E219279AE5
SHA-256297B3D520F1E280F320D43216EB8AAF71B0E5CC78C2FCF5C04BD0E0C75D9E784
Key Value
FileSize34400
MD512C55896368AF64D55F7729CE2295AB6
PackageDescriptionOCI 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.
PackageMaintainerPodman Packaging Team <team+podman@tracker.debian.org>
PackageNameconmon
PackageSectionadmin
PackageVersion2.0.25+ds1-1.1
SHA-1A34E5CE9872DA3DC62F4E5BDDF31C95883195539
SHA-2560FEE318D94B1C7B12A4F21D70833793DCC4A5B056C34BEC12D421D565339A568
Key Value
FileSize31572
MD560403275FD33E9C09C5E6EB4EDE9AAA2
PackageDescriptionOCI 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.
PackageMaintainerPodman Packaging Team <team+podman@tracker.debian.org>
PackageNameconmon
PackageSectionadmin
PackageVersion2.0.25+ds1-1.1
SHA-12227DE12FC98CFD3C889B33B7B75860345DD6950
SHA-2562566025A88AD8C3D0331FBEE19AB0B7F01E037AAE6FBDD7B3B381E098DAAE11E
Key Value
FileSize31572
MD5B63E968BE71A917982C9E16AC02E9A9E
PackageDescriptionOCI 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.
PackageMaintainerPodman Packaging Team <team+podman@tracker.debian.org>
PackageNameconmon
PackageSectionadmin
PackageVersion2.0.25+ds1-1.1
SHA-1CA4083DB0491B22F1374E1F4EB1641660CE3580C
SHA-2565EB1AAF6A8ED6E92A97632E4A8A76240AE418E1AA5C7E78BFC0530510B4D9FDF
Key Value
FileSize33540
MD59E6DB088DC586D8E608E2376E87CCA81
PackageDescriptionOCI 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.
PackageMaintainerPodman Packaging Team <team+podman@tracker.debian.org>
PackageNameconmon
PackageSectionadmin
PackageVersion2.0.25+ds1-1.1
SHA-19295F8C5FD17E3F060C7178DCD86F196D37485F2
SHA-256ABC388BFE8A7AA4945034A0013DBCBF5DFC7E528336EA116A92E5452AF8254A7
Key Value
FileSize32120
MD5169C6B8F4BF63F7FF515DD31E019F94D
PackageDescriptionOCI 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.
PackageMaintainerPodman Packaging Team <team+podman@tracker.debian.org>
PackageNameconmon
PackageSectionadmin
PackageVersion2.0.25+ds1-1.1
SHA-1E7EC21A61A8BDCAEDB13370174418B33BAC1FF95
SHA-256F06FE5CABC7C57B5E97F29BAD91491D2FF27DA3A8409320CC319A9890243E529
Key Value
FileSize34852
MD57181F82C0A8231E8BF0C9421A9797C62
PackageDescriptionOCI 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.
PackageMaintainerPodman Packaging Team <team+podman@tracker.debian.org>
PackageNameconmon
PackageSectionadmin
PackageVersion2.0.25+ds1-1.1
SHA-1F4C49B22D0CBC5BCAC015D56DC869E85ECBA65CE
SHA-256F82A647D22BB56EB57665E8BD18CC0875F8F37A1E93AE060E63261B547F86E69
Key Value
FileSize32180
MD592BD58A4DF432B96B71AAB9BBB7D88A9
PackageDescriptionOCI 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.
PackageMaintainerPodman Packaging Team <team+podman@tracker.debian.org>
PackageNameconmon
PackageSectionadmin
PackageVersion2.0.25+ds1-1.1
SHA-198E0A8F6298F19EE848122615507A1885AB6AE87
SHA-25608C15C4652275B845CD7F391B90104434A5FA2AADCCF8FC7279C21BAF2B8748D