Glidein installer provided init.d/condor does not kill condor_shared_port
One of the features of the installer is to create the
file for ease of administration.
When stopping Condor, it hardkills all condor processes (safest way to avoid timeout hell).
However, the installer has not kept up with time, and is not killing ALL the processes anymore.
In particular, it is missing
I verified that this is broken for the Q&A installer... have not looked into the ini-based one.
#3 Updated by John Weigand about 8 years ago
It appears to work ok but I must admit I have not closely verified it.
Was going to this morning but discovered most of the certs I use
expired 3 days ago. So have to wait some. Am on vacation until
the 16th after today but may be able to look at it before I leave.
#7 Updated by Parag Mhashilkar about 8 years ago
- Status changed from New to Resolved
This is not an issues with the ini installer. Ini installer does not create /etc/init.d/condor. If I remember correctly this was done to support multiple installation of condor on same node without breaking anything or trying to stop condor processes from some other service.
There is a CONDOR_LOCATION/condor that you can use to start and stop condor services. It correctly stops the shared port daemon.