-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/07/13 14:40, Mark Hahn wrote:
> do you really find users who decide to choose their own nodes?
In the past yes, they've come from places who either haven't had a
queuing system or who haven't use HPC before and haven't read the docs
or been to
>> I would argue that this sort of restriction is BOFHish
>
> I think of it more as protecting user jobs from other users who are
> new to HPC and probably well meaning (or desperate to get jobs running).
do you really find users who decide to choose their own nodes?
to me, there are three quite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/07/13 08:10, Mark Hahn wrote:
> I would argue that this sort of restriction is BOFHish
I think of it more as protecting user jobs from other users who are
new to HPC and probably well meaning (or desperate to get jobs running).
As the users pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/07/13 19:02, Kilian Cavalotti wrote:
> - Slurm: https://computing.llnl.gov/linux/slurm/faq.html#pam
The Slurm documentation is actually at:
http://slurm.schedmd.com/faq.html#pam
The Slurm developers have no access to the LLNL pages to update
I would argue that this sort of restriction is BOFHish
(and, if it needs to be said, unattractive for that reason.)
of course, if you really have widespread abuse by users
running amok, and who persist once informed of the rules,
well, you have no choice.
creeping BOFHism is relatively subtle, ins
Hi all,
I'm late to the discussion, but if I correctly understands John's
question, it's about *dynamically* restricting user access on compute
nodes where they have no job running, rather than just preventing all
users to log on any node.
For that matter, a great solution is to use a PAM module
Hi all,
I'm late to the discussion, but if I correctly understands John's
question, it's about *dynamically* restricting user access on compute
nodes where they have no job running, rather than just preventing all
users to log on any node.
For that matter, a great solution is to use a PAM module,
On 23/07/13 17:13, Chandler Wilkerson wrote:
> We currently use a pam access setup like that:
>
> # cat /etc/security/access.conf
> -:ALL EXCEPT admins root:ALL
>
> Then if users need access to the node while running jobs, we can do a
> prolog/epilog that adds another line to allow in the user (the
