11 pointsby metriclogic6 hours ago6 comments
  • akhila000027 minutes ago
    Should overlap prevention live at the scheduler level or inside the script with lockfiles?
  • metriclogic5 hours ago
    Happy to answer questions about how the parser handles edge cases, or why I chose client-side only. Also curious — do you manually check for cron overlaps today, or just find out when something breaks?
  • ramesh99003 hours ago
    At what point does cron complexity justify moving to a proper job scheduler like Airflow or Temporal?
  • stop505 hours ago
    That is why i moved to systemd timers. I can manage relationships and prevent duplicate runs.
    • metriclogic4 hours ago
      Fair point — systemd timers solve this properly. This is for the massive installed base that isn't migrating anytime soon.
  • karthik2911935 hours ago
    How does it handle jobs that run on different servers? Like if I have 5 machines all running their own crontabs, the overlap problem is actually across hosts not just within one crontab.
    • metriclogic4 hours ago
      Single host for now. Multi-host is a real problem but wanted to nail the common case first — most people don't know they have single-host overlaps until something breaks.
  • keerti_ece5 hours ago
    Honestly? Find out when something breaks. Had a backup job and a DB vacuum running at the same time last year, took down prod for 20 minutes before I figured out what happened. Wish I’d had something like this.
    • metriclogic4 hours ago
      20 minutes of downtime is exactly the kind of thing this was built to prevent. Hope it helps next time.