Comment 1 for bug 839659

Is there any reason this script needs to take a lock at all? All it's doing is looking up bits in config, and then running process-job-source.py for each one - and that script takes its own locks. I can't see how just deleting the locking from process-job-source-groups.py would cause any trouble.

If this approach sounds sensible, then I have a patch, since I'm thinking of adding a new FREQUENT job.