Result for 28F683C4025B185416D3F9CC53F81D69B4DA1ADB

Query result

Key Value
FileName./usr/bin/pps
FileSize16136
MD59D5A8309AE4AE663FC3BAA6B269117ED
SHA-128F683C4025B185416D3F9CC53F81D69B4DA1ADB
SHA-256449E8146F45516E3ECA6A49A706177C630350A9F1FC67F29C4C4D0916E11FAB6
SSDEEP192:GgPDzRYWHZ0W/iRKj8DqfYhKc48FuXg5yrEdWPox6jMVZ8Gl9hGjk+L176/ETxnn:BPWyZ0rNXp0U/kDt1
TLSHT15D72EA0BD79ACAB9C75CC6B048570BB56273B570EB3087271790A5741D037889D2FAB9
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
MD5A82A396A94022F8CA288EE08F16E24D7
PackageArchx86_64
PackageDescriptionThe Process Management Interface (PMI) has been used for quite some time as a means of exchanging wireup information needed for interprocess communication. Two versions (PMI-1 and PMI-2) have been released as part of the MPICH effort. While PMI-2 demonstrates better scaling properties than its PMI-1 predecessor, attaining rapid launch and wireup of the roughly 1M processes executing across 100k nodes expected for exascale operations remains challenging. PMI Exascale (PMIx) represents an attempt to resolve these questions by providing an extended version of the PMI standard specifically designed to support clusters up to and including exascale sizes. The overall objective of the project is not to branch the existing pseudo-standard definitions - in fact, PMIx fully supports both of the existing PMI-1 and PMI-2 APIs - but rather to (a) augment and extend those APIs to eliminate some current restrictions that impact scalability, and (b) provide a reference implementation of the PMI-server that demonstrates the desired level of scalability.
PackageMaintainereatdirt <eatdirt>
PackageNameopenpmix
PackageRelease1.mga9
PackageVersion4.2.0
SHA-15040D749D5C72DF53152694B6F20A3B8D7E19566
SHA-256E345EEEED0B5F2717765C85780AAB42E7D184704B12F4297EE143DFBC43EFF9F