Re: [HTCondor-users] Graceful stopping of condor_submit

["Weatherby,Gerard" <gweatherby@xxxxxxxx>]

Thanks, works perfectly.

 

SUBMIT_REQUIREMENT_NAMES = Retire

SUBMIT_REQUIREMENT_Retire = False

 

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Jaime Frey via HTCondor-users <htcondor-users@xxxxxxxxxxx>
Date: Tuesday, August 22, 2023 at 4:37 PM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Cc: Jaime Frey <jfrey@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] Graceful stopping of condor_submit

*** Attention: This is an external email. Use caution responding, opening attachments or clicking on links. ***

The best way to do this is to set a submit requirement (configuration parameter SUBMIT_REQUIREMENT_NAMES) that denies new submissions (either all submissions or those from specific users). This allows existing jobs to run and the users can still manage those jobs (i.e. run condor_rm, condor_release).

 

 - Jaime

On Aug 22, 2023, at 2:45 PM, Weatherby,Gerard <gweatherby@xxxxxxxx> wrote:

 

Is there a  graceful way of stopping users from submitting new jobs while still allowing condor_q to work as existing jobs finish? This is on an 8.8 system running the SCHEDD daemon locally.