(feat)support flock based locking for blender scripts

So locking is implicit using blender based on the name of the script to be run? Can blender scripts take arguments (eg. a restart box script that takes the search criteria for which box to run against)?

From Resque work I've done before, I'm used to locking being defined in the unit of work and not by the job execution system, so it feels a little funky to have blender throw locking around all jobs. That said, most jobs will want some locking. Maybe it's good enough to give the script someway to name the lock, which defaults to the name of the script itself.