Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] condor_status update time
- Date: Tue, 10 Oct 2017 10:22:46 -0500
- From: Todd Tannenbaum <tannenba@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] condor_status update time
On 10/10/2017 9:58 AM, John M Knoeller wrote:
To shut the daemons down cleanly, you can use condor_off -master. Or
you can send the condor_master a SIGTERM signal, which has the same
effect. Then you have to give the condor_startd and condor_master time
to shutdown cleanly. I believe that this can take as much as 2 minutes
if the condor_startd is running a job and the job doesnât respond to
SIGTERM, (or doesnât respond quickly).
Quick comment on the above:
If you do not want to be patient with running jobs, you could add the
"-fast" flag like so:
condor_off -fast -master [node name]
which typically shuts things down within a few seconds, killing the job
with SIGKILL if needed. This should be what happens when you do a
'systemctl stop condor'.
regards,
Todd