Result for 52E2BC8BCA58FA2476CE02119D211E0E271E37E5

Query result

Key Value
FileName./usr/share/doc/oomd/README.md
FileSize3546
MD547A1A821014D25164284C4BE19F5E034
SHA-152E2BC8BCA58FA2476CE02119D211E0E271E37E5
SHA-256523A63E4F04EF61D6359432AA84C334ACE545D8C8183DE28D8121429661BCA2A
SSDEEP48:CE+0TfQ/2COud0GmNkMNbLUE8pfSVAg/ta5oqFJ1VrOXa7I03o4thgz5YXpY:q0TYuHuVZTpfSLta+qFJ4vYy
TLSHT1E77197576315283B1F7312A291EA13F4AE38817DA284E5D4C5EF466CEB0246583BFC2A
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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
MD52F621DF6B98DF7E814E805646E2DC98D
PackageArchs390x
PackageDescriptionOut of memory killing has historically happened inside kernel space. On a memory overcommitted linux system, malloc(2) and friends usually never fail. However, if an application dereferences the returned pointer and the system has run out of physical memory, the linux kernel is forced take extreme measures, up to and including killing processes. This is sometimes a slow and painful process because the kernel can spend an unbounded amount of time swapping in and out pages and evicting the page cache. Furthermore, configuring policy is not very flexible while being somewhat complicated. oomd aims to solve this problem in userspace. oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.
PackageMaintainerFedora Project
PackageNameoomd
PackageRelease1.el8
PackageVersion0.5.0
SHA-1C28CEF8EF863E8A396A9FA976683E84D3E32391D
SHA-2564951E8327C469848E1F35C07CFB1B59491CBD6E063CEFB896930B48B3D071787
Key Value
MD573D4E3CEA225CA16C76BA70EB55E7BC1
PackageArchx86_64
PackageDescriptionOut of memory killing has historically happened inside kernel space. On a memory overcommitted linux system, malloc(2) and friends usually never fail. However, if an application dereferences the returned pointer and the system has run out of physical memory, the linux kernel is forced take extreme measures, up to and including killing processes. This is sometimes a slow and painful process because the kernel can spend an unbounded amount of time swapping in and out pages and evicting the page cache. Furthermore, configuring policy is not very flexible while being somewhat complicated. oomd aims to solve this problem in userspace. oomd leverages PSI and cgroupv2 to monitor a system holistically. oomd then takes corrective action in userspace before an OOM occurs in kernel space. Corrective action is configured via a flexible plugin system, in which custom code can be written. By default, this involves killing offending processes. This enables an unparalleled level of flexibility where each workload can have custom protection rules. Furthermore, time spent livedlocked in kernelspace is minimized.
PackageMaintainerFedora Project
PackageNameoomd
PackageRelease1.el8
PackageVersion0.5.0
SHA-150B56BD309285D2269848832964DFE5BF248E3ED
SHA-256254341D88ECC137702ED124E2A7B0F241EE7C1F60FF6758848E037FBCD935DA9