[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] stopping a startd on negotiator node (fwd)

On Tue, 19 Jul 2005 10:38:10 -0500 (CDT)  Steven Timm wrote:

> I changed the condor_config.local file to eliminate the STARTD in
> DAEMON_LIST, and did condor_reconfig such that condor_config_val
> DAEMON_LIST shows that it is missing the startd.  But the startd is
> still going.

from the manual:


------- Forwarded Message


This macro determines what daemons the condor_master will start and
keep its watchful eyes on. The list is a comma or space separated list
of subsystem names (listed in section 3.3.1). For example,


NOTE: This configuration variable cannot be changed by using
condor_reconfig or by sending a SIGHUP.  To change this configuration
variable, restart the condor_master daemon by using
condor_restart.  Only then will the change take effect.

------- End of Forwarded Message

> Can I kill the startd without restarting condor?  Or is there a
> nicer way to do it.  (There are 2 jobs still running on this node
> but I don't mind killing them).

as mentioend, you can use "condor_off -startd" on the machine, and
then the master won't restart it automatically (if you just SIGTERM'ed
it, the master would restart it).  if/when the master is restarted
(either condor_restart, a machine reboot, whatever), your new
DAEMON_LIST setting will be used and it won't spawn the startd.