Result for CD6433515711189B7622099C05EB98A38CC1F47B

Query result

Key Value
FileName./usr/share/doc/ruby-posix-spawn/changelog.Debian.armel.gz
FileSize227
MD5775DA2971F1FE9A82986045CB56D51A2
SHA-1CD6433515711189B7622099C05EB98A38CC1F47B
SHA-256AB912A0C821CDDD5D6C4EB90A7C9F2749751ADA7F113405BF2F5CFF83DB0A597
SSDEEP6:XtfmXbf1aYjRzo16U7iiF0gnjRgUIUGJ9qyLIWpEP36OX/n:X5mLpl06U7iiFzRg7fJ9/h+KOX/
TLSHT1A2D0975470C28F0EDF4450B47A533A24C80922193B00EA8EE01A7009201988C810A85D
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
FileSize23684
MD5FD4ED8B5AB9574E7D7C14FFE7112AAD6
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-19D24D3E6DC06569B4532D2A2076C51BCB72D1556
SHA-25626C396E9D9137D8EDC9FC15429AEF8EA2F1597C7DEB990A6D7C1E130CB7267EF