Open choksi81 opened 10 years ago
Author: zackrb This fix has been implemented but not yet committed because harshexit.portablekill(pid) function does not actually kill the processes running under the other user's account. This is because the windows_api function that kills programs within the harshexit.portablekill(pid) function can apparently only kill processes assigned to the user running harshexit.py
Working with Armon to see if there is a fix for this.
Right now runonce.py looks under the user's CURRENT_USER registry key. The values stored here, though, are specific to this user. Thus, if seattle is running under a different user account name, then the pids for seattle processes/locks will be stored under the seattle user account's CURRENT_USER registry key.
Thus, seattle does not get stopped.