Result for 58B5A3F4C88C5FE9688E2F92AF30DA4411D554D7

Query result

Key Value
FileName./usr/share/rubygems-integration/2.7.0/specifications/posix-spawn-0.3.13.gemspec
FileSize1835
MD50FD1D79551295334319337EF6E7E364B
SHA-158B5A3F4C88C5FE9688E2F92AF30DA4411D554D7
SHA-2565FDEB655F1AC79D85D38F352D911E979FF42C36458E115D67226024827D5A68E
SSDEEP24:Zkb/Yk8omenWNkRh4eKmPI4vdetshRDWasE2jAUMXMW6/2gA:uwrenMuh4eFI8khtdcMW6/2P
TLSHT10D31572D4C53B885B5702F81C4C0186193AFEDA9BA8D4D5867959F3E038378E57C7EB2
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
MD5DCA6F602120725AE27B480FF7B45AA76
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.)
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameruby-posix-spawn
PackageSectionruby
PackageVersion0.3.13-3
SHA-110405126A635E09C41012B75B4FCD0A52CCA4E8F
SHA-25641FAADDBE3BBB7EADEA9B88DDFED1CC09B49604422C817F723054BF7ECA00D24