Result for 36106D2EEDBB5FA21E7EF99DADDD9316FBB3C7C4

Query result

Key Value
FileName./usr/share/doc/ruby-posix-spawn/changelog.Debian.arm64.gz
FileSize228
MD5D942F0A6F14C508CD4486E5F0082C127
SHA-136106D2EEDBB5FA21E7EF99DADDD9316FBB3C7C4
SHA-256361EC426AA254BE23F6EC1528C0117897AD8BAD622E31BE602CBEB4EA1298BCC
SSDEEP6:Xt/vxgxaee0HJDMTMUacuqaAFFHakC8XUp5x74H4mZ+0OZU/n:XtIm6cuqDHakpEp5xkN+0T
TLSHT1E0D0A7754352D045AC94007EC6C3EC42EC047B8B93A7A65455B6EF0A6946CB54ACCC2C
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
FileSize23272
MD5EB461CCDF6D155A65142AE5E0C14D752
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-2+b1
SHA-130646535B5F70D30CFEE2362659256DEA0FA21B1
SHA-256DF7CAD44605CD835C9F0E881CCB664490446C74ED20313C8919E29E6B3B724F3