[GE users] Automatic qlogin on the head node

templedf dan.templeton at sun.com
Tue Sep 29 21:01:58 BST 2009


+1.  That's exactly what I was going to suggest.

Daniel

rayson wrote:
> What you need is to disable normal users from logging onto the head
> node, so you need to disable rsh, telnet, and ssh for non-root users.
>
> SGE itself does not rely on system daemons to provide interactive
> sessions, so interactive SGE jobs would still work normally after
> disabling non-root access.
>
> And the hardest part : you just will need to teach your users that
> qrsh to the head node is the only way to access the host.
>
> Rayson
>
>
>
> On 9/29/09, rafaarco <rafaarco at ugr.es> wrote:
>   
>> Hello everyone,
>>
>> First of all, sorry for posting this if it's already been answered
>> somewhere else, but I wasn't able to find any satisfying answers.
>>
>> My question is the following one: Is there any way to force an
>> interactive job submission (a forced qlogin) when users log into the
>> head node of a cluster, so that sessions on the head node can be
>> controlled by SGE? In other words, every time a user logged in, a new
>> interactive job controlling the session would automatically be created,
>> in order to prevent users from overusing the resources on the head one.
>>
>> I'm considering some alternatives such as adding the qlogin command at
>> the end of .bashrc or .cshrc (although this could be easily bypassed if
>> a user wanted to), adding a qlogin at the end of /etc/profile
>> and /etc/csh.login (I don't know if this could cause a conflict with
>> commands in users' login files) or using the ForceCommand option
>> included in the last versions of OpenSSH (so that it could be
>> shell-independent).
>>
>> I also tried changing the user login shell to a Bash wrapper that was
>> something like "qrsh /bin/bash", but it didn't work. No prompt was
>> returned, although the session was started indeed.
>>
>> There might be some solutions, probably better than these. Maybe a
>> feature of SGE to naturally do this that I overlooked. Perhaps someone
>> has already implemented such a thing.
>>
>> Any suggestions or comments?
>>
>> Thanks in advance,
>>
>> Rafa
>>
>> ------------------------------------------------------
>> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=219675
>>
>> To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].
>>
>>     
>
> ------------------------------------------------------
> http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=219678
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].
>

------------------------------------------------------
http://gridengine.sunsource.net/ds/viewMessage.do?dsForumId=38&dsMessageId=219680

To unsubscribe from this discussion, e-mail: [users-unsubscribe at gridengine.sunsource.net].



More information about the gridengine-users mailing list