Result for 54C305E79E397530497D09910525FA9123874863

Query result

Key Value
FileName./usr/share/doc/ruby-posix-spawn/changelog.Debian.s390x.gz
FileSize231
MD582FBB3285D06F6E8DC73888FCD7C5B4A
SHA-154C305E79E397530497D09910525FA9123874863
SHA-256D38C35B9BDF5D03E1C98AC33E7D88954505F4AAEBCD7F5A692F7F6B87F65A52F
SSDEEP6:XtWMSBNsAn7oKVW+VBKdjdNchQEQSqo56S7UzcHWw1wuwn:X6sAnjrCdx8ko58/qRwn
TLSHT166D02300F7381F83D09D0C717A7C089C0C3146601E24AF0CC008E7C833DE0813040CE2
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
FileSize24342
MD579D9FA4222EC82F58F7800EFF6C390B3
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-11C47ECA54A1CFC484EDF333905C7106D8346A464
SHA-256AEB7BC38B1D4C4D89BD39D91E232C3F45651E6A547D616E756F021E6DE0504EB