Q: You need to schedule a one-time task to run at 3:00 AM tonight (e.g., a database maintenance script). How does the `at` command differ from `cron` for this use case?
cron is designed for recurring scheduled tasks (e.g., every day at midnight). at is designed for one-time scheduled execution—it runs the...
#Linux #Allow user 'deploy' to restart nginx and read syslog only #L2 #SRE #Systems #Troubleshooting
🎙️ Candidate Opening & Architectural Context
""Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: at vs cron, one-time vs recurring scheduling.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
cron is engineered for periodic, recurring scheduled jobs (e.g. daily backups at 02:00 UTC). The at command is designed specifically for one-time deferred execution—it queues the command once, executes at the designated time, and automatically removes itself from the queue.
echo "/usr/local/bin/db-maintenance.sh" | at 03:00- Syntax Examples:
echo '/usr/local/bin/patch.sh' | at 02:00 tomorroworat now + 3 hours. - Key SRE Takeaway:
atavoids polluting crontab with transient one-off tasks that risk being forgotten and executing unintentionally weeks later.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: cron is designed for recurring scheduled tasks (e.g., every day at midnight). at is designed for one-time scheduled execution—it r."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: cron is designed for recurring scheduled tasks (e.g., every day at midnight). at is designed fo
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement