Result for 18B4A8C445AAC417D2F9CCE2B08363ACEFCB36D6

Query result

Key Value
FileName./usr/bin/pmix_info
FileSize28436
MD5B8300E9181C0E4A5D767698EA115E768
SHA-118B4A8C445AAC417D2F9CCE2B08363ACEFCB36D6
SHA-256594D4AA8BB023DB33F045D106C65B3EB59512FDD8D017DBA8FADDCCFDA48B338
SSDEEP768:/9+LYCLsQITLqYrLDLxT0UDbAe5gj7aAxb0/PvUJYd2HmABR7Ak5uejnq6AmIZDU:F+LYCLsQITLqYrLDLxT0UDbRz5VNJxwb
TLSHT122D2D697B806C5F7C8E00B74634ACF4633B36674E7FBA601D40806744B5EA8E493BE5A
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
MD52167DA5C8AEB4CB637992AFA32126F12
PackageArcharmv7hl
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-10CFE98D19BD3583CDBFCB2126AF2E38E132A258C
SHA-2565E96819A031B9C4739650CDD4014720B12193AFF2CDD4D75DF336E5C04A4B4CA