Result for 6903356628CD042BAC98ED9714203372B0CAF28E

Query result

Key Value
FileName./usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/posix_spawn_ext.so
FileSize14496
MD57EB3170B4189FF76DED3F0989ED556AD
SHA-16903356628CD042BAC98ED9714203372B0CAF28E
SHA-256C48A09801F97386178B5CCDCCFBD8FA5FA2704E44034F4B98B67ED7337322171
SSDEEP192:Rtq8pG7EvojE3zO2uk9BQK5/VzcBhv9zQUF8hY6e7TaLqNCW:3G4veE+k9BQ4/VQ1UUF8iieN
TLSHT11852C60FA6D09EB9D1D8833455E746315EB1B8F0FA23135B0218A7362E927584B2F77A
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
FileSize24222
MD5EDB339126C5248744C27F8259A4A28DE
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.9-1
SHA-1F4F2FDF6D9C3F8D8824A113FBE3C1F7B1EFF1761
SHA-256310F5A8C538C51059A86514B5A42DB34EC7F4EDEC29EE56B5027679DA185843D