Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

What ways are there to prevent users from starting long running, resource intensive processes on the headnode of a Rocks cluster?

I've tried:

  • asking politely
  • setting the nice level in limits.conf to 19. Didn't have the expected effect. Processes run at 19 nice level, but machine still becomes unresponsive (maybe memory)

I'm considering:

  • putting time/memory constraints in limits.conf
  • breaking the links to popular programs like /bin/python. Seems clunky

Other thoughts:

  • Banning offending users is not an option
  • Sometimes users need to run interactive sessions. This can be done by launching one through the console with qrsh, so there's really no need to run anything on the head node
share|improve this question
add comment

1 Answer

We disallowed logins to our headnode and installed the gridengine client utilities on user workstations. Users can run qrsh from their workstation to get an interactive session on the cluster and still use qsub and qstat.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.