cronquot
cronquot is a command/library for quoting cron execution.
You can create a list of cron scheduler with this tool.
Only you should do is preparing your cron data.
Usage
Preparation
To run cronquot, you have to make directory and put cron files exported from crontab -l.
File names should server names like below.
$ tree
crontab/
├── server1
├── server2
└── web1
CUI
From command, you can use only one command.
# You can set start time and end time.
$ cronquot -s 20170201010000 -e 20170201020000 -d crontab
After this, result file will export as 'result.csv'.
Python sample source code
You can use this with only python2.7
from cronquot.cronquot import Cron
c = Cron(start='20170101000000',
end='20170101101000')
for cc in c:
print(cc)
Installation
$ pip install cronquot
Licence
- MIT
1 maintainer
Metadata
1 maintainer
Release files for cronquot 0.1.4
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 |
|---|---|---|---|---|
| cronquot-0.1.4.tar.gz | 5.0 kB | Without provenance | Details for cronquot-0.1.4.tar.gz |
Release files / cronquot-0.1.4.tar.gz
| Download URL | cronquot-0.1.4.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6914b0e3fff8f60a27c8f83686df44f4c4719d7b6fca62413063630f0d099f88
|
|
BLAKE2b-256 checksum How to use checksums |
c42029a35aa5fc1cdeace18ce4a39e805476b3c92c667807407d7d917f1f3897
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cronquot 0.1.4
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.
