Result for AD380FB6374C141A4B620FF676D9B4C159842D31

Query result

Key Value
FileName./usr/bin/ib_acme
FileSize69288
MD50AE73039D268CF42FE4035B133D4EA59
SHA-1AD380FB6374C141A4B620FF676D9B4C159842D31
SHA-25688861816BF405398E38E701100E31860C60AA34880CECF018AEA12EC2315EBFB
SSDEEP384:4qZMtsadjM8gUslk1A8tucba+d//pDr6mORVBQO4xaEjiKWbymBMD9efHhCDpj:D6BK/SKyucblfDrrjTIGiKuNhC
TLSHT18B63D8DA37442003E08126B09DB51BBCF7EC52D261663957BA0E46378F72E74ADBE2C5
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
MD5B8AA46681425A3FAE320B94EC3CD54DB
PackageArchppc64
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.fc24
PackageVersion1.2.0
SHA-1266CA0F9677BC35E7A43B8DD91C65EAA77FF3D8F
SHA-256E3A620BED186641E0656CAAF921296F8C382EAABE9DEE35929AEB5EA72DE3283