Re: [Condor-users] condor_submit not respecting umask

[Jaime Frey <jfrey@xxxxxxxxxxx>]

On Mar 8, 2006, at 5:50 PM, Mitch Murphy wrote:

> i must run all the condor daemons as non-root. i was lucky enough to
> obtain permission to install condor on several machines at school,
> there's no way i'd be granted root access to all these machines.
>
> here's the problem ...
>
> - condor daemons run as user condor
> - user johndoe call condor_submit from a working directory below /
> home/johndoe
> - users condor and johndoe both have umask 0000
> - condor creates jobname.1.0.stderr.out and jobname.1.0.stdout.out
> owned by johndoe with permissions -rw-rw-r--
>
> and i get ...
>
> WARNING: File /home/johndoe/test/jobname.1.0.stdout.log is not
> writeable by condor.
>
> why does condor insists on creating stderr/stdout files with -rw-rw-
> r-- when i've tried so many ways to get -rw-rw-rw- ?
>
> any comments appreciated.

If Condor is started as a user other than root or the user submitting  
jobs, you're going to run into permissions problems of this kind. If  
you can't start Condor as root, then you should start a separate  
condor_master and condor_schedd for each user running as them. You  
can have multiple condor daemons running on the same machine, as long  
as they have separate log and spool directories.

Running the central manager and execute daemons as 'condor' isn't a  
problem, as long as you're using Condor's file transfer mechanism.

+--------------------------------+-----------------------------------+
|           Jaime Frey           | I used to be a heavy gambler.     |
|       jfrey@xxxxxxxxxxx        | But now I just make mental bets.  |
| http://www.cs.wisc.edu/~jfrey/ | That's how I lost my mind.        |
+--------------------------------+-----------------------------------+