The script attempts to detect thrashing situations and temporary stop rogue processes, hopefully before things get too much out of control, hopefully giving a sysadm enough time to investigate and handle the situation if there is a sysadm around, and if not - hopefully allowing boxes to become just slightly degraded instead of completely thrashed, all until the offending processes ends or the oom killer kicks in.
As of 2014-09, the development seems to have stagnated - for the very simple reason that it seems to work well enough for me.
Metadata
Release files for thrash-protect 0.13.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| thrash-protect-0.13.0.tar.gz | 27.3 kB | Without provenance | Details for thrash-protect-0.13.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| thrash_protect-0.13.0-py3-none-any.whl | Python 3 | none | any | Details for thrash_protect-0.13.0-py3-none-any.whl |
Total release size: 50.0 kB
Release files / thrash-protect-0.13.0.tar.gz
| Download URL | thrash-protect-0.13.0.tar.gz |
|---|---|
| Size | 27.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37a5d056fd45f9e19b31a0b7123e3abb478525b50fae4a67e289ab3178db66a9
|
|
BLAKE2b-256 checksum How to use checksums |
64f25efbca4da19f3ff87d6ea3e6fd21c602bb17e81dad5efce7089c8734736e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.28.1 CPython/3.8.0
|
Release files / thrash_protect-0.13.0-py3-none-any.whl
| Download URL | thrash_protect-0.13.0-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c8fd14c3fbed84eb576f1af423fc30138b050621662aab31ac6073909c94c9c8
|
|
BLAKE2b-256 checksum How to use checksums |
b043229367daeec017788a872637618bf723e41f30d2090d21bdcb204fcac7b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.28.1 CPython/3.8.0
|
Security for thrash-protect 0.13.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.