Result for 97B8A740033B6CC084EB4A0B722260D07F0A72A1

Query result

Key Value
FileName./usr/sbin/ibacm
FileSize74728
MD5C3DC3D584CC13531065009199787F856
SHA-197B8A740033B6CC084EB4A0B722260D07F0A72A1
SHA-25666AE1DCF9C42CFE2909512EAA90414290CE2E3CDC1077F3A1B48FFAEC4A3030A
SSDEEP1536:Dnh4GP4aM1pq8F4jfkDzmbWe5FLrUZMBXn7tA:Z4q9QY95FLrBn7tA
TLSHT1FC732BADE697C4F0D09240F50AFF5B51326080E49213E7F7EA0EF66AB8B16596D17338
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
MD50316BEEE0E7D213531F7B74A0A31D3DF
PackageArchi686
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-18309552521448750EE47FB993DAFBC845E35A7FC
SHA-256F54E0E95C511EDD34CC8B08B7C17250145D2F3F6497302082588F6EB2CCA4333