Result for F7874A7BB42F0AAC59C570415D9DC4E9DEFEF455

Query result

Key Value
FileName./usr/lib/s390x-linux-gnu/ruby/vendor_ruby/2.3.0/posix_spawn_ext.so
FileSize18728
MD5C6C42671B26DD0696DD5127E24AECFA1
SHA-1F7874A7BB42F0AAC59C570415D9DC4E9DEFEF455
SHA-2561737AAE5313273510CA680A1832EE01153F122F36129B774EE94CE687A77D5A1
SSDEEP192:ocUV8py5EMzmlLu8c/+0KUaZB1sdHoocC1aThlQAeEYQdvN5cA:FU1SMzml1UAB2om1aVlSgc
TLSHT1CC82824ADB31D6AAC9F87B32424F957593BB5C30BB8D4B15779CEB501DB37004928B22
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
FileSize24342
MD579D9FA4222EC82F58F7800EFF6C390B3
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.11-1+b2
SHA-11C47ECA54A1CFC484EDF333905C7106D8346A464
SHA-256AEB7BC38B1D4C4D89BD39D91E232C3F45651E6A547D616E756F021E6DE0504EB