5 ms·

Terrible hack, or building a solution from parts, i can't really tell the diff.

• mikeash 10y ago
  I think what turns it into "terrible hack" for me is the fact that it won't properly handle the situation where the machine reboots after firing the cron job and before the sleep completes. Having an extra process sitting around for potentially hours doing nothing but waiting also seems ugly. Neither is particularly important though....
  • zzzcpan 10y ago
    Try scheduling a job with "at" in that crontab entry, some systems have it installed by default and jobs persist across reboots. The at jobs are executed through cron themselves.
    • mikeash 10y ago
      Good idea! I'll keep that in mind if I ever try to do it.