Result for F54054C2D87BC09B6454F3635B9104FD87863432

Query result

Key Value
FileName./usr/lib/s390x-linux-gnu/ruby/vendor_ruby/2.5.0/posix_spawn_ext.so
FileSize18200
MD5AB7A577AA00CE0966AA600C4EF2274A7
SHA-1F54054C2D87BC09B6454F3635B9104FD87863432
SHA-25639DCD4C544591D8FB911DAC7C65B3C6C78BEC2DF7A182F654EA9B1CDE7413271
SSDEEP192:OJ58IYEkWtyFstgtSNUt1hov5/ZySUeh9M2W0XKdorm5mLOG:07HkWY2tfNe05QSUejMQDO
TLSHT1FB82924EAB31C9EFD8F47B35019F96B993BB4C31B7864A547B5CD3512DA33008A26A31
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