Skip to content
This repository was archived by the owner on Oct 13, 2026. It is now read-only.

docs: say that a scheduled job wakes the nook, and what it costs - #12

Merged
vish727 merged 1 commit into
mainfrom
eng-37-cron-docs
Sep 28, 2026
Merged

vish727 merged 1 commit into
mainfrom
eng-37-cron-docs

Conversation

@vish727

@vish727 vish727 commented Sep 28, 2026

Copy link
Copy Markdown
Contributor

cron was documented as "runs a command on a schedule" and nothing else, which left the question an author actually has unanswered: does it run when nobody is using the nook?

Until nookcloud/nookd#43 the honest answer was no — cron runs inside the machine, and the machine is stopped after ten idle minutes, so a nightly job on a nook nobody opens at 03:00 never fired. With that change it does, and this says so, along with what it costs in machine time: an entry every minute keeps the nook awake all the time; a nightly entry costs about ten minutes a night.

Worth being explicit about, because an author choosing * * * * * when 0 * * * * would do is now choosing something with a price.

Part of ENG-37

@vish727
vish727 merged commit 7147bd7 into main Sep 28, 2026
1 check passed
@vish727
vish727 deleted the eng-37-cron-docs branch September 28, 2026 06:47
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant