Result for 514D6230A8C4895F1A705A7B34DB8B1913D6D42F

Query result

Key Value
FileName./usr/share/doc/ruby-posix-spawn/changelog.Debian.s390x.gz
FileSize226
MD5ED1CDE15D57249CA35A727C5F5805889
SHA-1514D6230A8C4895F1A705A7B34DB8B1913D6D42F
SHA-256F75EBF92A4D202BE4246CA26F75970BEFFBE4867B441D9FD77EC790CBECEB254
SSDEEP6:XtM4aPuzjkhw1IZztdh+N19xnlzMlFDpbOrlloIcSRLq0Nt:XGSjkhFRtdhOHJatb+dcSLqIt
TLSHT1C6D0A70E1752E9C9839B1534C41B8229958C6E9680AFE6A35A1D24B47975A0CEC465B4
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
FileSize23688
MD50E126FD64605CD5B1EE3081B0DD0E577
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-14981A2112ACBC80CE4598200428460303747C4C4
SHA-2569637D42EDCBC8F37E4803CD2D628C6EBC31E4E5EEA927C657D45EBE1515F0ABB