Result for 2B6EF623C358053808A64FF6CE7F455BAD2B9BCA

Query result

Key Value
FileName./usr/lib64/ibacm/libibacmp.so
FileSize62424
MD5D94B3B3568BB6F55153908B9BFD531B8
SHA-12B6EF623C358053808A64FF6CE7F455BAD2B9BCA
SHA-256AAC82A05B2A5C5F08DFE67BBE0201FD67CC1F52F074D7CDBDDDA9EAB66EB601F
SSDEEP768:+3vNn0ckMU8Es0ckMU8Es0ckMU8Es0ckMU8EP3/nvXfHP3/nvXfHP3/nvXfHP3/z:e6qKkgmQEJzJjQPSHPBBvy
TLSHT1D9531C9BF25108BCC0D0E430CBABD7137A36F458A6311A2F1E848BB96D56E785E2FD15
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
MD5E03B2636886981ED8DC3D27CFC45F1DD
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
PackageRelease1.fc32
PackageVersion28.0
SHA-17E23FECC7B32CBD25633DF4067A6E9CB47D87CCB
SHA-256F0294C8565ACA3C6E93378460EBF52F6E09DB3EB30421C10BAC5848A486CA147