Result for AAA21577373020C5C41F3B40EA1A6262C65925E3

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.7.0/posix_spawn_ext.so
FileSize9480
MD5A39B7F5913E8BBC25B53AC20F6DE69D7
SHA-1AAA21577373020C5C41F3B40EA1A6262C65925E3
SHA-25673FC9BB88EF997193F4E96BEC2E3C25E085FDCF2623AAB00515AE8804A1A7ABE
SSDEEP192:BFn8ZcepxUKWKTy1JtJ1U52N5SXQiTfIJD5s0btPXp:BFycE5yTS52N5CJQEs
TLSHT18C1293CCE5D37C33D8F9863D846B0E0163B2C58FAA979F13165876610E5A28C8CABF15
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
FileSize23300
MD527AFED4559AFCD001DA6F4D798F75F52
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-12D67C5A210D54760C57F28122279D4E9B8ABCECE
SHA-256D47EBCCA22CE65AF2BF84AA1D5D34474D3A465A76F771871087A22299EEDFE22