Result for E5A1D7CDC93932C1E3857E8C9F55BDB70A1E931B

Query result

Key Value
FileName./usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0/posix_spawn_ext.so
FileSize14176
MD5B5EFFC941061A9A4016104C04E19294D
SHA-1E5A1D7CDC93932C1E3857E8C9F55BDB70A1E931B
SHA-25645E14C01C849E5F27EA53D9CE0B7F5A9360D7249E98050BBB8A693A44330033F
SSDEEP192:RwNss8p2dElFFV4zbGorM2zkheyRn+twDtcPwRCcR:cs02l2GorMWkhrHtNZ
TLSHT18E52A706E26148BFD095433805EB817A5EF1BDA2E62217DB1314FB323D8776C0729B5A
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
FileSize23444
MD564F438CD21F99305F163366D01FE580B
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-2~bpo9+1
SHA-144D335200116A7CDA29C53F704C3DB793E78504A
SHA-25643F11365DFE80B49671DA225C053B24501409DE4BAA405FB639B2BBDB66A4A30