Ensure temp files are only accessed by the correct thread

It appears the problems may have been caused by threads simultaneously
accessing the same temp files, such that they were executed multiple times
on certain hosts and never on others. This change prevents this by appending
the hostname to all temporary files, so they will only be accessed by the
correct thread.
A work in progress, worker script, and an updated template
This should handle SGE cluster hook-up, needs more testing
Update SGE template
Updated script for testing
Do some sudo fiddling and add some sane defaults for check intervals
Set workflow engine for oozie-sge and remove invalid thread parameter
Try re-mounting mysteriously unmounted mounts
Further separate passes for template to allow for integration tests
Merge branch 'feature/glassfish' into feature/sge_workers
Further fixes to allow oozie to "work out-of-the-box" and NFS fixed itself with the re-ordering?
Strange, we really need to make sure the NFS mounts work otherwise integration tests totally fail
Revert "Ensure temp files are only accessed by the correct thread"

This reverts commit bafb474a6c2de0bd20dea3503358af138f59394f.
Merge branch 'develop' into feature/sge_workers
Add defaults for workflow definition length and retries maximum
Set default user-level retry
Adapt oozie startup to use postgres instead of embedded oozie
Merge remote-tracking branch 'origin/feature/sge_workers' into feature/sge_workers
Merge pull request #9 from SeqWare/feature/sge_workers

Feature/sge workers  I currently have a 2 node cluster launching on AWS to test this.  In the mean time the changes look OK so I'm going to merge this into develop.