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

Re: [Condor-users] SYSTEM_PERIODIC_HOLD



if I do a -HUP to the shadow's won't that restart other things?

I am always worried about restarting stuff on condor. Is there a table
in the manual that shows what is safe to restart and what isn't?



On Thu, Nov 5, 2009 at 10:09 AM, Dan Bradley <dan@xxxxxxxxxxxx> wrote:
>
>
> Todd Tannenbaum wrote:
>> Steven Timm wrote:
>>
>>> system_periodic_hold is executed on the machine that reruns
>>> the condor_schedd.  I think you have to restart the condor_schedd.
>>>
>>> Steve
>>>
>>
>> Restarting the schedd will certainly work, but a reconfig is all that is
>> required.  So you could reconfigure "on the fly" by making the change in
>> the config file and then doing
>>    condor_reconfig <name of submit machine>
>> from a machine with ADMINISTRATOR authorization according to the config
>> file (by default this means the central manager).
>>
>
> That's true for idle jobs but not for running jobs.  (Perhaps this is an
> oversight.)
>
> The workaround is to send SIGHUP to all running shadows in addition to
> running condor_reconfig.
>
> --Dan
>
> _______________________________________________
> 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:
> https://lists.cs.wisc.edu/archive/condor-users/
>