Result for 6DA05D8EB3F6C296E2F3448DC0B56B4D6F668CA2

Query result

Key Value
FileName./usr/lib/aarch64-linux-gnu/ruby/vendor_ruby/2.7.0/posix_spawn_ext.so
FileSize14104
MD5495693A083549FF5B7E73867290B7E77
SHA-16DA05D8EB3F6C296E2F3448DC0B56B4D6F668CA2
SHA-25625463D0773C2BD14B16119C069A3C0C6A0333BF179E851D5B615DCD72EE71DF6
SSDEEP192:sUWNp89CADCgm3e875BO7qCcgTjdcEz658Pe5A:sAhm9tvcqCxmEz9W
TLSHT14E52A954FA45C93BC2C5D3F95E9A82B9A33351A8E34743D3A604CF485E8336D8E36598
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
FileSize23768
MD588DB4CD7C0E935B3EBD6F8DD05164BA3
PackageDescriptionRuby Implementation of posix_spawn(2) for faster process spawning The posix-spawn library aims to implement a subset of the Ruby 1.9 `Process::spawn` interface in a way that takes advantage of fast process spawning interfaces when available and provides sane fallbacks on systems that do not. . `fork(2)` calls slow down as the parent process uses more memory due to the need to copy page tables. In many common uses of fork(), where it is followed by one of the exec family of functions to spawn child processes (`Kernel#system`,`IO::popen`, `Process::spawn`, etc.), it's possible to remove this overhead by using the use of special process spawning interfaces (`posix_spawn()`, `vfork()`, etc.)
PackageMaintainerDebian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
PackageNameruby-posix-spawn
PackageSectionruby
PackageVersion0.3.13-3+b1
SHA-1E8F9683EDE43BBEFA313F0A062C2D8685A8EA957
SHA-25679D54906A44D0B13EF62AF5E40939594866741569015A50ABFF12CD9CE0E4B01