This provides the features one wants from a daemon for arbitrary commands providing a service:
process id (pid) files for both svcd and the service command
filesystem visible status (command running, service enabled) via cs.app.flag
command restart if the command exits
command control (stop, restart, disable) via cs.app.flag
test function to monitor for service viability; if the test function fails, do not run the service. This typically monitors something like network routing (suspend service while laptop offline) or a ping (suspend ssh tunnel while target does not answer pings).
signature function to monitor for service restart; if the signature changes, restart the service. This typically monitors something like file contents (restart service on configuration change) or network routing (restart ssh tunnel on network change)
callbacks for service command start and end, for example to display desktop notifications
I use this to run persistent ssh port forwards and a small collection of other personal services. I have convenient shell commands to look up service status and to start/stop/restart services.
See cs.app.portfwd which I use to manage my ssh tunnels; it is a single Python programme running multiple ssh commands, each via its own SvcD instance.
Metadata
Release files for cs.app.svcd 20170906
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 |
|---|---|---|---|---|
| cs.app.svcd-20170906.tar.gz | 6.5 kB | Without provenance | Details for cs.app.svcd-20170906.tar.gz |
Release files / cs.app.svcd-20170906.tar.gz
| Download URL | cs.app.svcd-20170906.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
882d4baa76c95f50b6f5110d2f0bce28877c8cc8542c29ae896b1cbdafe9481a
|
|
BLAKE2b-256 checksum How to use checksums |
ba4dcce675e327acc573e2d58b8c5c46af18f189dd3df8a97782d2ed673197f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cs.app.svcd 20170906
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.