RE: [Condor-users] central manager

[bgore@xxxxxxxxxx]

You can also set "START = FALSE" in the local config file for this machine. That's what we prefer instead of not running the STARTD because that way we can still 'see' the machine in the pool, query classAds and stuff like that.

If you do want to go w/the 'no startd' approach, changing the daemon_list can be tricky. After you do so, you'll probably want to 'condor_off', wait until all daemons are gone except condor_master and then 'condor_on'.

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Andrew Zahn
Sent: Tuesday, January 25, 2005 1:28 PM
To: Condor-Users Mail List
Subject: Re: [Condor-users] central manager


Erik Paulson wro


> On Tue, Jan 25, 2005 at 01:48:00PM -0600, Andrew Zahn wrote:
> 
>>How do you keep jobs from running on the central manager?
>>
> 
> 
> On the central manager, set
> 
> DAEMON_LIST = MASTER, COLLECTOR, NEGOTIATOR
> 
> If you want to be able to submit jobs from your central manager, put:
> 
> DAEMON_LIST = MASTER, COLLECTOR, NEGOTIATOR, SCHEDD
> 
> -Erik
> 
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx 
> http://lists.cs.wisc.edu/mailman/listinfo/condor-users

So essentially, if the startd is running then jobs can be processed on 
the machine? I have made the changes you recommended above and have 
restart condor, but I still see the central manager in my condor_status. 
In addition I see the processes running:

condor    5088     1  0 14:21 ?        00:00:00 condor_master -f
condor    5162  5088  0 14:25 ?        00:00:00 condor_collector -f
condor    5163  5088  0 14:25 ?        00:00:00 condor_negotiator -f
condor    5164  5088 30 14:25 ?        00:00:05 condor_startd -f
condor    5165  5088  0 14:25 ?        00:00:00 condor_schedd -f

_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx http://lists.cs.wisc.edu/mailman/listinfo/condor-users