Result for 7E987F0FD662BCBCBC74264332CD6FAF618E8213

Query result

Key Value
FileName./usr/share/doc/oomd/docs/core_plugins.md
FileSize8333
MD53D488B651A56A84BF0FA4334A69EF6C0
SHA-17E987F0FD662BCBCBC74264332CD6FAF618E8213
SHA-256C2F503A405BE44DE8C20B3FB5A92BEB2EA326496D7474C415F96AAEFDE59A381
SSDEEP192:W/ILtrFBcfr5WHnKctO7J0qtXacZ1Oiqy8ZUKN5/OU+2tLb:WW8dWHy7JXtXL1dX8+mQ3e/
TLSHT1D2023226791933AA62E702F1311BF38A0A3A4359E251BC1CE05D51E03B176668FBF5DA
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
MD5D47126105764F7FBE4353E5D99F17B34
PackageArchaarch64
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.fc32
PackageVersion0.3.2
SHA-1098414B90DDD13B9B4AA3C8D84511925AC8DEBDB
SHA-256A56F883598906BA9C77C6B46027C1102434CEDB4DB73F18F7B120E3BC9702DC4
Key Value
MD57382473E6DC775B052C297C62CCBB598
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.fc32
PackageVersion0.3.2
SHA-12DBB3A63827BB2584A2EF30A2A4BB25476BCCDDB
SHA-25639AC9C1719E71D60840C9295246DE5766BAD5124F2DF1435D7BC8473BE3573B7