Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 555756 - sys-process/cronbase: run-crons: sub-jobs should be run with timeouts
Summary: sys-process/cronbase: run-crons: sub-jobs should be run with timeouts
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All All
: Normal enhancement (vote)
Assignee: Anthony Basile
URL:
Whiteboard:
Keywords:
Depends on: 157547
Blocks:
  Show dependency tree
 
Reported: 2015-07-24 05:53 UTC by SpanKY
Modified: 2019-03-29 13:08 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SpanKY gentoo-dev 2015-07-24 05:53:02 UTC
+++ This bug was initially created as a clone of Bug #157547 +++

run-crons has long had behavior where a long running job (perhaps by accident) will starve further execution until that job finishes.  for example, do:
  # printf '#!/bin/sh\nsleep 100000000' > /etc/cron.hourly/long-job
  # chmod a+rx /etc/cron.hourly/long-job

once that job is launched by run-crons, then no more jobs in cron.hourly will be launched until it exits.  this includes both the current `run-crons` as well as follow up launches of run-crons by cron.

we should update run-crons to execute each job with a timeout suitable for the category we're executing.  probably want to make it a command line flag so people can set the timeout higher if they really want this behavior.