Result for C653D0A65E9E0D41D5589A53BEBB18CA45A51D24

Query result

Key Value
FileName./usr/share/doc/ruby-posix-spawn/changelog.Debian.amd64.gz
FileSize242
MD5F9FDC30301806543A138538877985DFB
SHA-1C653D0A65E9E0D41D5589A53BEBB18CA45A51D24
SHA-256A72B165945E299F44B01697935E33FECEFEF34A9B367AD6035FEE704C2CB3E49
SSDEEP6:Xtwh0Pf+/PdNQr1X1t42sf4rvXAZERRu1T7+xpnzLlD:XE0H+3dN0N1tSQzA63m7+7zLF
TLSHT177D0977AD2949DE0C21893292BF831D2C6E5A402C881A1E0200233A278210F01E4A0D1
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
FileSize24276
MD5A5DBF707ED400BF171D9623DE905447D
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-1E4CA56DD084DFCD7D238A6B1EF562F6A4AB19A9A
SHA-256C976118D31347654B608DFF6B813FDCBBD358709EAE16DCF3E82F91A3AFECE64