I have answers to your questions.
Yes, you can configure the permissions of the directories that are
created (provided you have at least version 8.1.3 or version 8.0.7
(to be released)). There is a new setting JOB_EXECDIR_PERMISSIONS
that controls those permissions. Take a look at the entry for it in
There is a new command called condor_tail that can be used to watch
the stdout/stderr for a job.
On 03/18/2014 01:29 PM, Szabolcs
First of all, thanks for the assistance!
Wow, that's an old version!
Yeah, if it ain't broke, don't fix it... ;) The only problem is
that when you find that it is actually broken, you might be off
with years of releases...
Here's what I would do:
I did what you suggested and the first step seems to be working
nicely, with one minor exception:
1) Upgrade a single worker node and only allow it to accept jobs
from a test user. See if this works.
7.5.5 used to create the startd worker directories in /tmp with
permissions 755 while 8.1.4 creates them with 700.
I know that these are not "public" directories but we have some
jobs that run for a long time and we let the users look into the
work-in-progress stdout/stderr logs by using a GUI. Can we somehow
configure what permission these directories created with? (BTW the
file in there are still 755, so its just the directory that blocks
other users.) Or is there an "official" solution for getting these
logs like the fetching tools for system and user logs?
HTCondor-users mailing list
To unsubscribe, send a message to
htcondor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at:
HTCondor & Open Science Grid
Center for High Throughput Computing
Department of Computer Sciences
University of Wisconsin - Madison
4261 Computer Sciences and Statistics
1210 W Dayton St
Madison, WI 53706-1685
+1 608 265 5736