[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Condor-users] restricting access to certain condor commands



I’m about to let some test users loose on a small linux cluster and it occurs to me that I’m going to want to restrict which condor_* commands they can run.

On the only submit node, all condor_* commands are in the /opt/condor/bin/ directory. Can I simply modify the permissions on these files so that regular users can only run e.g. condor_submit, condor_status & condor_q, and I (as admin) become part of the group owner who can run them all?


Or is there some internal command-calling by condor that will be severely shafted by this sort of change?





(I seem to remember a similar topic on this list a few months back but couldn’t find the thread. Pointers to a searchable archive of this mailing list are also appreciated)


Dr Steven Platt

Bioinformatics Support Coordinator

Statistics, Modelling and Bioinformatics

Health Protection Agency

Centre for Infections

61 Colindale Avenue




************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************