Result for B716E064D4A8F958D5D5BB09A351521A28C5386F

Query result

Key Value
FileName./usr/share/doc/ruby-posix-spawn/changelog.Debian.s390x.gz
FileSize235
MD53D19FF2431675C777F1945362810EAAD
SHA-1B716E064D4A8F958D5D5BB09A351521A28C5386F
SHA-25668D564A9901CA79581F656D065F3D5E4FB213B2FBF5908330B4023EFFDB14DDC
SSDEEP6:XtPeuHk14suHHxG/0AR6jZFaiHP4f2RPl2HC2HmoJMl:XJeuc4sWG/0AR6jWNfsIHLHBCl
TLSHT164D023240F5A36F0C04DB3F10FD1EAE4F0F820700493843881471206F4463641D9C0F2
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
FileSize23884
MD5EDEBCD66D59389830BA87CDC2D647C5F
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-108048098C3F705D5B2DCA2B36C6DE5CDF1DA909E
SHA-256A4F40F2BBDDD62750D089262A1A7BE6E9D40440D529547FB965DC4B5C66BCF89