Result for 2A8F86FF9A552A9A8EDC8D10D409D898F66FAED3

Query result

Key Value
FileName./usr/share/rubygems-integration/2.5.0/specifications/posix-spawn-0.3.13.gemspec
FileSize1990
MD560934830F9B8EFD39ADA969BB818F28A
SHA-12A8F86FF9A552A9A8EDC8D10D409D898F66FAED3
SHA-256066A80D77720B53F596213070F1030609ADAC92D50B8DCBE3EB31B3918A38E4C
SSDEEP24:Zkb/Yk8omen0NkRh4eKmPI4vdetshREWasE2wEx50Wi/ej/2gA:uwrenyuh4eFI8DhtwEn0Wi/ej/2P
TLSHT11A41731D4C53B8A5A5702F81C4C0046187AFEC95BA8D4D5877A99F3E038379E17D7EB2
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
FileSize23032
MD5F5E8C5F6203F627FFA8CE457F4A56C13
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-167DF83986E30BAE45435C1E6FB69C35E0DCC121F
SHA-25614EEA5AFCCB22E207432E808B59180F292B8EA2D489706F795C467A5EF7028B5