I'd agree that "length of manual" is a poor heuristic for complexity. Condor is super-customizable, and they document those options pretty extensively. To the

I'd agree that "length of manual" is a poor heuristic for complexity. Condor is super-customizable, and they document those options pretty extensively. To the direct point, they've even started highlighting the use of condor as "condor cron" in the Open Science Grid to run monitoring applications: http://vdt.cs.wisc.edu/releases/1.10.1/notes/Condor-Cron.html http://vdt.cs.wisc.edu/releases/1.10.1/notes/Condor-Cron.htm... Without that, I'd say it would be a slightly masochistic exercise to take a big system like condor and try to make it a cron replacement; while it clearly has that capability, if that's not one of its use cases, it's going to be a real bear to force it into that configuration. I've been a fringe user of condor before, and it can result in some unfriendly "rejected your job for unknown reasons" situations.