I'm having problems with jobs not running with the correct umask and gid. Ideally I would like jobs to run on the remote machine with the same gid and umask that the user had when he submitted the job, but Condor doesn't retain umask and as far as I can tell it doesn't retain gid either. The plan for umask is to put a "umask 2" line into the /etc/init.d/condor script so that the condor_master starts with a umask we can live with, but it'd be better if this changed based on user umask. I'm not sure how to get it to respect gid; it seems to always run jobs with the user's default gid instead of the one that they are currently using.
Has anyone run into this before? Any ideas on how to fix this? I'm particularly interested in a solution for gid, since we have some sensitive data that needs to remain protected and switching it to the user's default group could cause problems.
Thanks a lot
This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.