Result for 52A1A1F83DE7C8020A836A19F283EC866D3CA382

Query result

Key Value
FileName./usr/lib64/ibacm/libibacmp.so
FileSize62192
MD5000E3D45101248AC9C3D039F4B248CB1
SHA-152A1A1F83DE7C8020A836A19F283EC866D3CA382
SHA-25675D9A9222530789460049E34BE02C0B6E841D8A7FA427F0E6A0D996BF3AF0F21
SSDEEP768:8l1RDyMU8Es0ckMU8Es0ckMU8Es0ckMU8EP3/nvXfHP3/nvXfHP3/nvXfHP3/nv+:8XkQpvYuHPNmuJrR5oAX7VyAX
TLSHT1F753F95BB2511CBDC4D0E830DB6BD313BA35F458A232191F2E888BB92D47E785E2ED15
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
MD54167C6850A983904B0D4BB23A0BFDB2C
PackageArchx86_64
PackageDescriptionThe ibacm daemon helps reduce the load of managing path record lookups on large InfiniBand fabrics by providing a user space implementation of what is functionally similar to an ARP cache. The use of ibacm, when properly configured, can reduce the SA packet load of a large IB cluster from O(n^2) to O(n). The ibacm daemon is started and normally runs in the background, user applications need not know about this daemon as long as their app uses librdmacm to handle connection bring up/tear down. The librdmacm library knows how to talk directly to the ibacm daemon to retrieve data.
PackageMaintainerFedora Project
PackageNameibacm
PackageRelease3.fc34
PackageVersion34.0
SHA-1DE24F53DC4077F6E89DD34FE389995A5BAABBEFF
SHA-256BBFD4DEB8701DB337F5541DC6C68386DD635835C81712B8D24364A1F5D25437D