Result for 503C58D48398F53CF137F64B62BA0D2F4F22FD69

Query result

Key Value
FileName./usr/sbin/ibacm
FileSize70800
MD5CA589DD0466FF2F42BF7665749B451B5
SHA-1503C58D48398F53CF137F64B62BA0D2F4F22FD69
SHA-25658EA73413E91219D52C673B0F73873E67B3880D787BDA1451B121C031935432D
SSDEEP768:2Lo2mNAtVdFN19ltVdFN19lw4goQYAIw4goQYAIw4goQYAIw4goQYAIDrzbjLT7S:6di4oTWgTWgzup3DlMeyT
TLSHT11063294BA151187CC4D1D931CB9BC3136776B85CA6323A1F1E84B2763D4AA3CAD6FE24
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