Result for ED5E848F25322A193622D8FFA99BBF2CD6E63955

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.3.0/posix_spawn_ext.so
FileSize9756
MD5F72F27CA95378B3064E5D82C7219F6C0
SHA-1ED5E848F25322A193622D8FFA99BBF2CD6E63955
SHA-256D4C9DF82FC2492B1BC7F63E0983F840D386561A20EA07DE3AE29CA311122AF0E
SSDEEP192:sDk8pPyf3ulKxN9ErQwWBWN24Rcg5std:sD5yIKxN9ErQhB7MCt
TLSHT14712B5C9A4E2DF33C4C2873C40CB8E1857B1C989AA678B13572C77E17D6A66C8C29F11
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
FileSize23756
MD509A5488E80EFF504F9DA8EEFABBB6684
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.11-1+b2
SHA-179FD3CF724C28F0769351DB4C31AF398BA5C6F81
SHA-256F71F696E97D1574A83BB866644212099EBB30FCFD98D0BDAD8E0496FEAC126CC