Result for 033CC81FB5417C2100A9A32C6B0B12E6A486BD10

Query result

Key Value
FileName./usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/posix_spawn_ext.so
FileSize14704
MD537DE61229984E026FE872E98E40B4C9B
SHA-1033CC81FB5417C2100A9A32C6B0B12E6A486BD10
SHA-256A28FC13C107992CA457C840C35ACA334A17EBA3E1B76E2D92B5D88562E49E15A
SSDEEP192:Rczl28pedE9sVFbWFZOd9ZkRd9l/OroOiUOwvvwn9i9I:+829SFtXkRd9ZOLiUNLI
TLSHT17162C60FA1904DBAE098833444DB44712EB168E1FF23575F0214BB763E927484B2FBAE
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
FileSize24570
MD5F993F32073A662AA5F8F8993AD3B3BC7
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-1A79061FC3E50E23965E372613D80A5C12C14EE97
SHA-256073FD3F74050F95CAA11B82A933D548F24399A7D2393125579C1700E01D21432