fd-leak-finder
fd-leak-finder helps you figure out why your unix process is using up too many fds.
To use it, generate strace output with a command something like this:
strace -q -a1 -s0 -ff -e trace=desc -tttT -ostrace.file $EXECUTABLE
Then pipe the resulting “strace.file.$PID” into fd-leak-finder’s stdin.
CAVEATS
It turns out that strace’s representation of this stuff is much more complicated than I thought, and I don’t understand why some of fd-leak-finder’s computations turn out the way they do. You can see “xxx weird” sorts of messages in fd-leak-finder. Hopefully it will be useful to you anyway! If you figure out how to improve it please let me know.
I guess parsing strace’s human-oriented output is a bad way to do this. I’m not sure what a good way to do it is, on Linux. On Solaris or OSX I suppose a good way to do it would be to use dtrace.
LICENCE
You may use this package under the Simple Permissive Licence, version 1 or, at your option, any later version. See the file COPYING.SPL.txt for the terms of the Simple Permissive Licence, version 1.
1 maintainer
Metadata
1 maintainer
Release files for fdleakfinder 0.0.3
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 | |
|---|---|---|---|---|
| fdleakfinder-0.0.3.tar.gz | 9.6 kB | Without provenance | Details |
Release files / fdleakfinder-0.0.3.tar.gz
| Download URL | fdleakfinder-0.0.3.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
661f1e87bdce51886e0c1d6334d47fb7c2fea10e4e57497b191920744a077246
|
|
BLAKE2b-256 checksum How to use checksums |
ff5499c4e961a535d2403275a348199bcc0bc8aa1aa961e7aa2c563743c27a49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for fdleakfinder 0.0.3
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.
