Deploy tooling that chowns storage to the web user (Deployer with
writable_mode=chown and an http_user differing from the worker user) left
the supervised master unable to reopen its own lock file after a deploy:
fopen fails with EACCES, which was reported as 'another Torque master
holds the lock' and sent the operator hunting a ghost process while the
program went FATAL.

The lock, reload-lock and PID files are now created group-writable (0664)
so a chown that keeps the group leaves them usable, and a lock file that
cannot be opened is reported as exactly that, permissions and all, instead
of as a held lock.