Result for D39596C3143911D3DD48DD032F47E9DC4E32D6C4

Query result

Key Value
FileName./usr/lib/ibacm/libibacmp.so
FileSize61740
MD598560E28E5324BEBD196243E1AC61190
SHA-1D39596C3143911D3DD48DD032F47E9DC4E32D6C4
SHA-256163046AB7F773E9FE3634998CB49F2271FEF05C04FBCF51B8FD1C9C09A588C12
SSDEEP768:Eltr+PfM4lCR7A2qlrFtKxXwwsugn23r9KXqL4cPfuTHcFA4UYf9n9RvZeIRnn8Y:cKPfrlz2YZzRvqmzcjrvUIREgf
TLSHT1AE5309ACBBE3C4F1E15295B016AB5BA234708144D227FBA3EF08F31674667953D1A339
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
MD5C6E79BFF5A3BC460A1A9FE8DCA1E8ECB
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.
PackageMaintainerCentOS Buildsys <bugs@centos.org>
PackageNameibacm
PackageRelease1.el8
PackageVersion35.0
SHA-1578FB33109B59BCEC29B52308CF9E36C5A3D4ECB
SHA-256B2D5B58D4E45FA666746A1913472407F7E94A352861D4E1184B3B8FCC3C833F5