| Key | Value |
|---|---|
| FileName | ./usr/share/doc/packages/haproxy/internals/api/list.txt |
| FileSize | 8980 |
| MD5 | EE7961C07A1DD0684AA1441442041453 |
| SHA-1 | 07989E45DAE2A3495099A8D9E6A28DF13AD8441D |
| SHA-256 | 87773D9B69CD3FD1143C36750D47415E17B4CF37A895C7321AD9C7D47D1D0216 |
| SSDEEP | 192:cjA16Zu1ze6GKya3gFtIjkzLEXcZ/ghDiHKPr3UF+a6elvdcC0t:cjpqzpGC3gFtkk06W3gFXllF6 |
| TLSH | T1C402C8263366177342DA835B591E61DAF75AC47D172065A03C8E427C3F82CB8E2BDAE1 |
| hashlookup:parent-total | 2 |
| hashlookup:trust | 60 |
The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| MD5 | 6D1E9350C28AD4F9E7422F8ED84DF4AA |
| PackageArch | x86_64 |
| PackageDescription | HAProxy implements an event-driven, mono-process model which enables support for very high number of simultaneous connections at very high speeds. Multi-process or multi-threaded models can rarely cope with thousands of connections because of memory limits, system scheduler limits, and lock contention everywhere. Event-driven models do not have these problems because implementing all the tasks in user-space allows a finer resource and time management. The down side is that those programs generally don't scale well on multi-processor systems. That's the reason why they must be optimized to get the most work done from every CPU cycle. |
| PackageMaintainer | https://www.suse.com/ |
| PackageName | haproxy |
| PackageRelease | 150600.1.5 |
| PackageVersion | 2.8.6+git0.f6bd011dc |
| SHA-1 | AED95A5E723D9B1A327397AC1044D061194846F6 |
| SHA-256 | 48A2E570D9F1515E15027E305E0A61BC707981807B88C902B6A680B8BB1FB7A2 |
| Key | Value |
|---|---|
| MD5 | 899AA04F29B852B0FF00ED8D9A41B331 |
| PackageArch | s390x |
| PackageDescription | HAProxy implements an event-driven, mono-process model which enables support for very high number of simultaneous connections at very high speeds. Multi-process or multi-threaded models can rarely cope with thousands of connections because of memory limits, system scheduler limits, and lock contention everywhere. Event-driven models do not have these problems because implementing all the tasks in user-space allows a finer resource and time management. The down side is that those programs generally don't scale well on multi-processor systems. That's the reason why they must be optimized to get the most work done from every CPU cycle. |
| PackageMaintainer | https://www.suse.com/ |
| PackageName | haproxy |
| PackageRelease | 150600.1.5 |
| PackageVersion | 2.8.6+git0.f6bd011dc |
| SHA-1 | AA0B3EAE4D81BB03DFB32155E2DB07663B637C87 |
| SHA-256 | 12B507572B82F290C2354C7B26D6D47921D0B58043A51B970FB851837BC81C18 |