Result for 5C5690199EE52D501863BFFDAE9854DE787C1C14

Query result

Key Value
FileName./usr/lib64/ibacm/libibacmp.so
FileSize62432
MD592CBC1E3A98B7EB33D57FBDF830859C4
SHA-15C5690199EE52D501863BFFDAE9854DE787C1C14
SHA-256B4F9A17C6A04AAC6F90D0317EAF5A8B6411BCCCF2B5957962864A47BB5299D00
SSDEEP768:D3ENn0ckMU8Es0ckMU8Es0ckMU8Es0ckMU8EP3/nvXfHP3/nvXfHP3/nvXfHP3/E:L7qKVgmQE9aJjQSU4BBty
TLSHT1BD531B9BB25108FCC4D0E430DBABD3237A36F018A6312A2F1E8497B56D56E385E2FD15
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
MD5EB929D78655DB273F683C1C3E9203757
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.fc33
PackageVersion31.0
SHA-163C0825B6169CB677FB5B1F8A6672CB6C2D2BFD1
SHA-25620164DB81D461B7BC647A165602EE7A0EA4567605C2DD8465454A39F99EB7992