Rather than banning them or publishing behaviour, we simply disable
their access to the queue and won't re-instate it until they have
contacted us to indicate they have rectified their ways.
eg. rather than enforce hard disk quotas, which may result in a job
loosing data, we simply detect when they are over quota and
automatically stop their access to the queue and send them an email
saying what has happened.
They tend to clean up quickly :)
Of course you need a tightly controlled system which prevents them
circumventing the queue.
Stu.
On 02/08/2006, at 6:58, Diego M. Vadell wrote:
Hi Jerry:
the other example is that use system call and ssh
to each node and run stuff and bypass the scheduler...
Torque 2.1.2 has just been released. It comes with a pam module
that, if I
understood it right, makes harder (though not impossible) for users to
bypass the batch system. The documentation is inside the Torque
tarball.
Maybe you can collect some logs and make a list of misbehaving
users. Then
you can warn the users that you are collecting that information, that
bypassing the system will degrade the performance for everybody,
and that
you may post that information. Sometimes the perspective of public
humillation makes wonders :)
But, be warned! its just an idea, Im not expert in treating users (or
anything else, for the matter).
Hope it helps,
-- Diego.
--
Dr Stuart Midgley
[EMAIL PROTECTED]
_______________________________________________
Beowulf mailing list, Beowulf@beowulf.org
To change your subscription (digest mode or unsubscribe) visit
http://www.beowulf.org/mailman/listinfo/beowulf
