CaoE - Kill all children processes when the parent dies
CaoE makes it easy to automatically kills all spawned children (and grandchildren) processes when the parent dies, even if killed by SIGKILL.
Usage
Simply call:
caoe.install()
at the beginning of your program.
How it works
When caoe.install() is called, it forks out a child process and a grandchild process. Both the parent and the child process will block, only the grandchild process will continue to run. The child process keeps checking the status of parent. If it found that the parent has died, it kills grandchild process (and grand-grandchild processes if there are any) and suicides.
Change Log
0.1.7
Fix a bug that child process will exit on any signal.
Drop support for python 2.6.
Use py.test and tox for test runner, drop dependency of nose.
Make tests more stable.
1 maintainer
Metadata
1 maintainer
Release files for CaoE 0.1.7
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 |
|---|---|---|---|---|
| CaoE-0.1.7.tar.gz | 3.3 kB | Without provenance | Details for CaoE-0.1.7.tar.gz |
Release files / CaoE-0.1.7.tar.gz
| Download URL | CaoE-0.1.7.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aff17421f13a55f295715096cb1a48f9dbb64ba7a44d022913339d6065f10a8e
|
|
BLAKE2b-256 checksum How to use checksums |
5482c7f39e38ea8c6b3a319c06b8c6d3778c3ffae74f17b156296b9825c4900d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for CaoE 0.1.7
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.
