Updates to the job by condor_qedit (or remote Condor-C) are made to the schedd's copy of the job. -If the job is currently running, the shadow, starter, and startd will not see these changes. This resulted in a Condor-C bug in which the Condor-C lease on a job is not correctly handled. However, that doesn't seem like a problem requiring deep changes. A fix is currently being investigated. +If the job is currently running, the shadow, starter, and startd will not see these changes. This resulted in a Condor-C bug in which the Condor-C lease on a job is not correctly handled. However, that doesn't seem like a problem requiring deep changes. A fix is currently being investigated (#452). Lack of updates being pushed out by the schedd has also caused problems for users who changed policy expressions with condor_qedit and then couldn't understand why the policy wasn't being enforced. This is not a common use case and could just be documented as expected behavior. Another idea would be to provide a convenient way to stop and restart the shadow, which would effectively update the job policy in the shadow. Lastly, the problem could be addressed by adding updates from the schedd to the other players in the system.
