Systemd generator for timer units
Generates systemd .timer and .service units to more easily add cron-like tasks to your system.
After editing the units, the tool can install them for you: copy them into
/etc/systemd/system or $HOME/.config/systemd/user (creating the directory if
needed), run systemctl daemon-reload, and enable and start the timer. The
install step is only offered when systemctl is available; otherwise the
generated units are left in the current directory.
After editing, the tool checks the units with systemd-analyze verify (when
that command is available), so syntax errors are caught before installation.
Usage
generate-systemd-timer unit-name
# Now two editors will pop up to allow you to customize
# Afterwards you'll find unit-name.service and unit-name.timer in the current folder.
# Finally, you'll be asked whether to install, reload and enable the timer.
1 maintainer
Metadata
1 maintainer
Release files for generate-systemd-timer 2.1.2
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 |
|---|---|---|---|---|
| generate_systemd_timer-2.1.2.tar.gz | 35.5 kB | With provenance | Details for generate_systemd_timer-2.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| generate_systemd_timer-2.1.2-py3-none-any.whl | Python 3 | none | any | Details for generate_systemd_timer-2.1.2-py3-none-any.whl |
Total release size: 40.6 kB
Release files / generate_systemd_timer-2.1.2.tar.gz
| Download URL | generate_systemd_timer-2.1.2.tar.gz |
|---|---|
| Size | 35.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e8478d231b4221fa1f46c18428879e33e8b570802848cb784a4615c141b0e8e
|
|
BLAKE2b-256 checksum How to use checksums |
30cf3b854195f0b13efde5be72e37e0db92e5b4d000b283e2f95cd442960f043
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 10, 2026.
Transparency logRelease files / generate_systemd_timer-2.1.2-py3-none-any.whl
| Download URL | generate_systemd_timer-2.1.2-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7ba32f066ab38ddeeb5de1b8bb7f52d368656c70be79259de4d78b959a68ff19
|
|
BLAKE2b-256 checksum How to use checksums |
dc81b132048abf40a75a5eb53c73ff3301c086a5c9ec33965611c2fc3960e588
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 10, 2026.
Transparency logSecurity for generate-systemd-timer 2.1.2
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for generate_systemd_timer-2.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 10, 2026.
Transparency logA 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.
