Description of problem:
Shutdown of the configd on windows
Version-Release number of selected component (if applicable):
win build #49
Steps to Reproduce:
1. condor_off -master
hangs or daemon hangs around
There was the idea of overriding the shutdown script with our own where if the pid-to-die = configd it will drop a file and wait for clean shutdown, otherwise it will call the original method of process shutdown.
*** Bug 589673 has been marked as a duplicate of this bug. ***
Pushed to FH config-tools repo as windows_shutdown branch. The new pidkill.bat doesn't invoke condor_softkill but could I suppose after the sleep. Lots o' room for improvement
Made a minor update to pidkill.bat to exit early if configd is gone.
During my testing I had noticed various shutdown scenarios which would cause the configd to simply hang.
Step 1: open a terminal navigate to <install_path>\bin\ & execute condor_configd.py
Step 2: open a second terminal navigate to the above path and use process explorer to determine pid of condor_configd.py -> python.exe
Step 3: type pidkill.bat <pid>
During failure conditions you will see pidkill.bat exit and condor_configd.py will still be hanging around.
All issues are resolved. The configd is able to restart condor, multiple times, via an even from wallaby. The configd will be shutdown each time correctly as well.
I've tested this on Windows 2003/XP x i386/x86_64 and it works. --> VERIFIED