/ 
Chronic-0.30
River stage zero No dependents

Changes for version 0.30

  • ``Ping'' constraint was introduced. The constraint sends a single ICMP ping to a given address and is considered met if an ICMP packet is successfully received. ``Ping'' can be used to ascertain that network connection is available and functional for tasks that depend on one.
  • ``Concurrent'' constraint was introduced. The constraint keeps a tab on the number of concurrent processes of a specified application. The constraint is considered met iff the number of processes running is less than the concurrency level. [Feature Request #1011911]
  • Reintroduced a ``safe_sleep'' time at the end of the scheduler's while() loop. This stops the scheduler to go into a tight loop, every time there is a few microseconds of latency between task_wait and Freq constraint.

Documentation

Chronic
A constraints-based, opportunistic, application-level scheduler.
emerge-later
Intelligent scheduling for Gentoo's emerge.

Provides

Schedule::Chronic
in lib/Schedule/Chronic.pm
Schedule::Chronic::Base
in lib/Schedule/Chronic/Base.pm
Schedule::Chronic::Constraint::Concurrent
in lib/Schedule/Chronic/Constraint/Concurrent.pm
Schedule::Chronic::Constraint::DiskIO
in lib/Schedule/Chronic/Constraint/DiskIO.pm
Schedule::Chronic::Constraint::Freq
in lib/Schedule/Chronic/Constraint/Freq.pm
Schedule::Chronic::Constraint::InXs
in lib/Schedule/Chronic/Constraint/InXs.pm
Schedule::Chronic::Constraint::Inactivity
in lib/Schedule/Chronic/Constraint/Inactivity.pm
Schedule::Chronic::Constraint::Loadavg
in lib/Schedule/Chronic/Constraint/Loadavg.pm
Schedule::Chronic::Constraint::NAME
in docs/TemplateConstraint.pm
Schedule::Chronic::Constraint::Ping
in lib/Schedule/Chronic/Constraint/Ping.pm
Schedule::Chronic::Constraint::Xscreensaver
in lib/Schedule/Chronic/Constraint/Xscreensaver.pm
Schedule::Chronic::Logger
in lib/Schedule/Chronic/Logger.pm
Schedule::Chronic::Tab
in lib/Schedule/Chronic/Tab.pm
Schedule::Chronic::Timer
in lib/Schedule/Chronic/Timer.pm

Other files