Result for 0A4029A1AD6C1DFC4AF58815444F69B9DE8E26C6

Query result

Key Value
FileName./usr/bin/ib_acme
FileSize49248
MD575AF39E9C057B0D139E32CE6FB1FFADD
SHA-10A4029A1AD6C1DFC4AF58815444F69B9DE8E26C6
SHA-256F431DE0F0A6DCA1D5F22FF13FB8A5E7766F541C4646385AA377CF9397C89BA62
SSDEEP768:1dU5wIg4QoAYw45g4QoAYwIg4QoAYwIg4QbTLD7zrjbTLD7zrjbTLDzAuvPtiklr:1dczqPtiklSxAZurgw2v
TLSHT1EA230806A9411438C051D933CFDF92173EB1F99DA2322B2F358CA3763F4BD265A5AA71
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