Result for 1A982DD44B1979037B2F6456930965B9881AA1AD

Query result

Key Value
FileName./usr/share/doc/ruby-posix-spawn/changelog.Debian.amd64.gz
FileSize223
MD55C99678AC7BC706C43BB0C6BA05B4D13
SHA-11A982DD44B1979037B2F6456930965B9881AA1AD
SHA-2568C2FAE59890F83D494F15C0A1F9BFC4887DED1864C1D92BE37CA231A604B2F34
SSDEEP6:XtjeOvtcacV6GtU64F2KHXGDYCoVTixvfLLcOmk9LVX3Ql:X1eOveacQGmfv3d9cfLL1Q
TLSHT126D0A70845C0E20B93B64AA0CA6BE844D7394B8366B6DA1B1A339CA85759A89594C29A
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
FileSize23964
MD525A06B231D6166936FD161363C339106
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-1516E885743B5C7F39EBC60D7C64289340E7A4AED
SHA-2568B30A03AD4115B466BB739C324E6CED2549976F48DEBB97F75820B24DF6E0248