Add cron next-run display and speed up timer lookup
This commit is contained in:
11 files changed
+328
-14
No files matched your search
+7
-3
@@ -54,9 +54,13 @@ written to stderr as `Note:` lines.
|
||||
$ schedls show backup
|
||||
```
|
||||
|
||||
Shows one job in detail: status, backend and scope, whether schedls manages it,
|
||||
the schedule, the next and previous runs, the command, the source paths, and any
|
||||
systemd extras (persistent, jitter, accuracy, working directory, environment).
|
||||
Shows one job in a field-oriented view: status, backend and scope, whether
|
||||
schedls manages it, the schedule, next and previous runs, the command, source
|
||||
paths, and any systemd extras (persistent, jitter, accuracy, working directory,
|
||||
environment). Human-readable cron next runs are calculated in the host's local
|
||||
timezone; cron previous runs and results remain unavailable because cron
|
||||
exposes no per-job execution history. To preserve the JSON document contract,
|
||||
cron `next_run` remains `null` in `--json` output.
|
||||
|
||||
### `new NAME`
|
||||
|
||||
|
||||
@@ -35,6 +35,15 @@ Periodic directories only contribute executable, run-parts-style file names.
|
||||
Every unrelated line is preserved exactly. `schedls` does not reformat, sort,
|
||||
normalize, or rewrite crontab content it did not create.
|
||||
|
||||
## Run times
|
||||
|
||||
For five-field expressions and calendar nicknames, schedls calculates the next
|
||||
cron occurrence in the host's local timezone for human-readable output.
|
||||
`@reboot` has no wall-clock next run. Cron does not expose per-entry execution
|
||||
history, so previous run times and results are shown as unavailable rather than
|
||||
guessed. To keep the stable JSON document contract, cron `next_run` remains
|
||||
`null` in `--json` output.
|
||||
|
||||
## Managed blocks
|
||||
|
||||
Jobs created by `schedls` in the current user's crontab live in a delimited
|
||||
|
||||
@@ -113,6 +113,6 @@ in CI.
|
||||
|
||||
## Availability, privacy
|
||||
|
||||
`0.2.0` requires `systemd-analyze` to create or validate calendar expressions
|
||||
`0.3.0` requires `systemd-analyze` to create or validate calendar expressions
|
||||
and refuses the operation if it is unavailable. `schedls` makes no network
|
||||
requests and collects no telemetry.
|
||||
Reference in new issue
Block a user