utils/at - spool/queue doesn't survive restart
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Maintainer: Officially (yet maybe outdated) @philenotfound or maybe @neheb and @krant
Environment: OpenWrt 24.10.0, r28427-6df0e3d02a
Version: 3.2.5
at saves jobs in /var/spool/cron/atjobs, but /var is symbolically linked to /tmp, so it doesn't persist across reboot.
Similarly, I believe that it saves output in /var/spool/cron/atspool, and that also wouldn't persist across reboot for the same reason.
Interestingly, and I think for the aforementioned reasons /var/spool/cron/crontabs is linked to /etc/crontabs where it does persist across reboot.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how at uses /var/spool/cron/atjobs and /var/spool/cron/atspool, then compare those paths with the persistent /var/spool/cron/crontabs link to /etc/crontabs. Confirm the behavior across a reboot and determine what persistence behavior is expected for queued jobs and their output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100