Result for 5792C80106BC1C2E7240DA9D8C4EC4CFDF2E6A38

Query result

Key Value
FileName./usr/share/doc/ruby-posix-spawn/changelog.Debian.armel.gz
FileSize237
MD5EC9E6143110728BCCEE785B6B517B678
SHA-15792C80106BC1C2E7240DA9D8C4EC4CFDF2E6A38
SHA-25612A0AADE24DDCA0CD7C942D688A1E6BA7E54E6D7F8F35CC805066B6C3CAE217B
SSDEEP6:XtBFVaCquinD4N6wmnyfHDEQUfuZ0VvJtbsx/G/n:XNx+nkIwb/DEQFmhd/
TLSHT1D1D09733C928946FE2E96B3A4F10082C302F25A249AF3E25262696F02007C92480F1FA
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
FileSize23324
MD5DB61DE81D761FE5CC0FBBC702F80713B
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-1907592A39CC136EEC9CF8DEDE6E9AE7340D416CD
SHA-25680CE587CF2BE384B884F84F1468BC5B5396C5103F84AC676A9BCAC0C0DED31F9