Result for 375FC1809282369235E0AE4EFCD0274E1CB40CBC

Query result

Key Value
FileName./usr/share/doc/oomd/docs/writing_a_kill_plugin.md
FileSize7519
MD5B43E3416A93A60C8F8AF08C3F9981F69
SHA-1375FC1809282369235E0AE4EFCD0274E1CB40CBC
SHA-2565246496D7E1C9EB15B5869B70D43AF2A25979F193A119D88590557177FE34E87
SSDEEP192:unVWEOCV6L4rVvmCwv/7bLtcj8t8Qu+ETs6k:uUEOCVC4hvmCi7Vcj8t8Uks6k
TLSHT195F1D725346E333637EE21E4408F4DE4A60A51B3E491F12BB53E61AA7FC183995F36D4
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