Re: [Condor-users] Restrict pool to a single submit machine

[Bachmann François <f.bachmann@xxxxxxxxxx>]

Pascal

I don't believe having a single submit machine is a Good Thing - it's going to be overloaded with startd processes (one for every job submitted), so it's  bound to be the bottleneck of your pool. 
It looks like what you need is some serious accounting within Condor, based on the user ID of the submitter (check http://www.cs.wisc.edu/condor/CondorWeek2006/presentations/tannenba_accounting.ppt for more details on group accounting and priorities).

François


-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx on behalf of Pascal Jermini
Sent: Mon 21-Aug-06 19:02
To: condor-users@xxxxxxxxxxx
Subject: [Condor-users] Restrict pool to a single submit machine
 
Hello all,

I would like to know if it is possible to have only one submit machine per
Condor pool. In other words, what we want to do is to avoid having rogue
submit machines in our pool, since we would like to have all our users to log
into our single submit machine for accounting purpose.

Six months ago someone suggested
(https://lists.cs.wisc.edu/archive/condor-users/2006-February/msg00270.shtml)
to put a restriction in the START expressions, in order to restrict the
execution of jobs coming from a known schedd (by the way, I guess that with
the new support of regexps it becomes trivial to perform the proposed
check...).
We are not sure if this method is reliable enough to avoid rogue submit
machines, as the job classad can easily be altered in order to make it likes
the job comes from a legitimate submit host...

any thoughts/advice on this?

thanks in advance,

Pascal
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at either
https://lists.cs.wisc.edu/archive/condor-users/
http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR

<<winmail.dat>>