Introduction
This package is based on Products.signalstack.
The one difference from the original product is a change to where the thread dump is output. This version of signalstack uses the python logging facilities to output the thread dump, rather than printing to stdout. Certain production setups don’t have access to stdout, i.e. when zopectl start is used.
This change allows access to the thread dump when stdout is not accessible, since in addition to writing to stdout, the thread dump is also written to the zope event log. ‘
Products.signalstackLogger is triggered in the same was as the original, i.e. by sending USR1 to a Zope2 instance.
The original Products.signalstack is intended to be used with supervisord, which retains stdout.
From the original README:
This package is a simple debugging tool for Zope 2 instances that are stuck. Unlike the z3c.deadlockdebugger and DeadlockDebugger this package also works if all threads in an instance are stuck.
If you send the USR1 signal to a Zope2 instance with Products.signalstack installed it will dump a stracktrace of all threads on the console.
Changelog
0.9 - December 11, 2009
Initial release of Products.signalstackLogger
1 maintainer
Metadata
1 maintainer
Release files for Products.signalstackLogger 0.9
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 | |
|---|---|---|---|---|
| Products.signalstackLogger-0.9.tar.gz | 2.5 kB | Without provenance | Details |
Release files / Products.signalstackLogger-0.9.tar.gz
| Download URL | Products.signalstackLogger-0.9.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6d7fd07b128c6bd45ce85fc96ee7a9544a0c96ef4a4dffd0d2a5fc88d4211293
|
|
BLAKE2b-256 checksum How to use checksums |
c6d4b2a90f2cf9de916f65e7795807f11577a481919188f02598d2fd122bd332
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.signalstackLogger 0.9
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.
