Result for 9523F7912EE322348E8CD0F8C517604FC806274E

Query result

Key Value
FileName./usr/share/doc/ruby-posix-spawn/changelog.Debian.mips.gz
FileSize228
MD5D963A31CF3B3DDD019A81C5570D42F45
SHA-19523F7912EE322348E8CD0F8C517604FC806274E
SHA-256B31F1A4B90704F9DC138EF2B56873B00815BD2A76DEE3D036A9445EE4F5978A4
SSDEEP6:XtH0ty2ETkpSX4GVduWNXSLLVsoO5hmX8Db9BebhRE+M0r:XV0gqpktUSX0soObNpBeNREn0r
TLSHT1C8D0A7342C6CD019D63E1036F3AAD88494694ACC4D804704E6A680AAA07F9D127B4899
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
FileSize23468
MD59C64AB4672272498EE0592B856A735CD
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-12A1F3C903E4330236DF2D87CEFD7473CCD5DB812
SHA-256F8F0507E63B97FD9D069B0A66F3E45D9130230440316CB7433CEB62DC58071A8