Parents (Total: 15)

The searched file hash is included in 15 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	31928
MD5	2033D6D2E104650E970F3F7A1918E37B
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.0.25+ds1-1.1
SHA-1	CED24628403F70920C27036FD623A5F45EDDD1AB
SHA-256	0BD606336E333BBB9FFD376560A7EB2D3A844E204EA0CA739E956FCFC01D932D

Key	Value
FileSize	34368
MD5	4B623F7ECC0FD0830C826A17C05F3232
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.0.25+ds1-1.1
SHA-1	78A2BE642AF753BCC58E659635A035E219279AE5
SHA-256	297B3D520F1E280F320D43216EB8AAF71B0E5CC78C2FCF5C04BD0E0C75D9E784

Key	Value
FileSize	34400
MD5	12C55896368AF64D55F7729CE2295AB6
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.0.25+ds1-1.1
SHA-1	A34E5CE9872DA3DC62F4E5BDDF31C95883195539
SHA-256	0FEE318D94B1C7B12A4F21D70833793DCC4A5B056C34BEC12D421D565339A568

Key	Value
FileSize	31572
MD5	60403275FD33E9C09C5E6EB4EDE9AAA2
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.0.25+ds1-1.1
SHA-1	2227DE12FC98CFD3C889B33B7B75860345DD6950
SHA-256	2566025A88AD8C3D0331FBEE19AB0B7F01E037AAE6FBDD7B3B381E098DAAE11E

Key	Value
FileSize	31572
MD5	B63E968BE71A917982C9E16AC02E9A9E
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.0.25+ds1-1.1
SHA-1	CA4083DB0491B22F1374E1F4EB1641660CE3580C
SHA-256	5EB1AAF6A8ED6E92A97632E4A8A76240AE418E1AA5C7E78BFC0530510B4D9FDF

Key	Value
FileSize	34852
MD5	7181F82C0A8231E8BF0C9421A9797C62
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.0.25+ds1-1.1
SHA-1	F4C49B22D0CBC5BCAC015D56DC869E85ECBA65CE
SHA-256	F82A647D22BB56EB57665E8BD18CC0875F8F37A1E93AE060E63261B547F86E69

Key	Value
FileSize	33540
MD5	9E6DB088DC586D8E608E2376E87CCA81
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.0.25+ds1-1.1
SHA-1	9295F8C5FD17E3F060C7178DCD86F196D37485F2
SHA-256	ABC388BFE8A7AA4945034A0013DBCBF5DFC7E528336EA116A92E5452AF8254A7

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	32120
MD5	169C6B8F4BF63F7FF515DD31E019F94D
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.0.25+ds1-1.1
SHA-1	E7EC21A61A8BDCAEDB13370174418B33BAC1FF95
SHA-256	F06FE5CABC7C57B5E97F29BAD91491D2FF27DA3A8409320CC319A9890243E529

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

Key	Value
FileSize	32180
MD5	92BD58A4DF432B96B71AAB9BBB7D88A9
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.0.25+ds1-1.1
SHA-1	98E0A8F6298F19EE848122615507A1885AB6AE87
SHA-256	08C15C4652275B845CD7F391B90104434A5FA2AADCCF8FC7279C21BAF2B8748D