===========
*Detect long-running processes and notify you when they're done.*
Using ``longtroll``
-----------------
``longtroll`` pretty much does what it says on the box. In order to start
detecting long-running processes, run ``longtroll.py bind`` in your shell. From
then on, when a long-running process in that shell finishes, your notification
command will be called.
Before you start using ``longtroll``, you need to create a configuration file.
A sample configuration file can be found in the repository as
``longtrollrc-sample``. Copy this file to ``~/.longtrollrc``, or create your own.
The configuration file takes two options: ``seconds`` and ``notify``, as
follows::
seconds 10
notify echo <cmd> (pid <pid>) completed | wall
``seconds`` is the number of seconds that a process has to live before it is
considered "long-running". ``notify`` is a command that will be run when your
process completes. The tokens ``<cmd>`` and ``<pid>`` will automatically be replaced
by the command and the PID of the process that completed.
Roadmap
-------
* Add a ``longtroll.py unbind`` command
* Allow configuration of the poll time
* Some kind of notification method for when a long-running process is detected
1 maintainer
Metadata
1 maintainer
Release files for longtroll 1.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 | |
|---|---|---|---|---|
| longtroll-1.0.tar.gz | 2.8 kB | Without provenance | Details |
Release files / longtroll-1.0.tar.gz
| Download URL | longtroll-1.0.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
319f326ebab170af3a9d1d9eeebe322cb6df9986d7d1aa207352156e65407f6e
|
|
BLAKE2b-256 checksum How to use checksums |
61128b709efa50a41326760a1ababb9339db6840331422952e9f7a34a1952e38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for longtroll 1.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.
