Result for FD71EF75C83CB1BF9890155F6B1B8E942DB557F0

Query result

Key Value
FileName./usr/share/doc/ruby-posix-spawn/changelog.Debian.mipsel.gz
FileSize231
MD55787AC9533049E8B1FB5604BCBD5F381
SHA-1FD71EF75C83CB1BF9890155F6B1B8E942DB557F0
SHA-25670985808CFB6259CC7A82F1FA6C3189447ACBCEA18E4D01D65F995A7E58A3F72
SSDEEP6:XtyiOk0bYDPerq+YI14E4FpJPHRnvp+y+d9qtx1d6P6:XlOFyezl9olx+yW2dk6
TLSHT11ED0235C5C430C0171BC65FCF741F4C307CD08132F0F6086C4E6824C12042A8C1C30E9
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
FileSize24192
MD536B3154F1EEA33C012392EA8CA3F5688
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-16CB9E8579491C8331B53854128C41B219EE0C7EE
SHA-2562102A2315ADBBD9029BED3E4A504A8E4DED6165551D518B9A1666C73E13D2E55