Close me before I can update myself



  • This is probably getting to be fairly standard stuff but it still irks me...

    While repairing an installation of VMware, the installer tells me to close VMware (not running, no tasks showing in task manager) so that it can update VMware. Hmmm, if I close the installer...

     



  • @snoofle said:

    This is probably getting to be fairly standard stuff but it still irks me...

    While repairing an installation of VMware, the installer tells me to close VMware (not running, no tasks showing in task manager) so that it can update VMware. Hmmm, if I close the installer...

     

     

    I seen plenty of times where the process is gone from taskman, but the process is still alive in windows, for a while. 



  • @unklegwar said:

    @snoofle said:

    This is probably getting to be fairly standard stuff but it still irks me...

    While repairing an installation of VMware, the installer tells me to close VMware (not running, no tasks showing in task manager) so that it can update VMware. Hmmm, if I close the installer...

     

     

    I seen plenty of times where the process is gone from taskman, but the process is still alive in windows, for a while. 

     

    I've had firefox do that to me a few times.  If you try to launch FF while you've got one of those zombie processes running in the background, it throws a relatively descriptive dialog at you explaining the issue, and refuses to start until you've killed the zombie.



  • @merreborn said:

    @unklegwar said:
    @snoofle said:

    This is probably getting to be fairly standard stuff but it still irks me...

    While repairing an installation of VMware, the installer tells me to close VMware (not running, no tasks showing in task manager) so that it can update VMware. Hmmm, if I close the installer...

     

     

    I seen plenty of times where the process is gone from taskman, but the process is still alive in windows, for a while. 

     

    I've had firefox do that to me a few times.  If you try to launch FF while you've got one of those zombie processes running in the background, it throws a relatively descriptive dialog at you explaining the issue, and refuses to start until you've killed the zombie.

    But the Firefox zombie is still visible in the process list (second tab, as opposed to the applications list, first tab, which is really nothing more than a task bar with the "close this window" menu command duplicated as a button). The OT sounded as if the alleged VMWare process wouldn't be visible anywhere at all.



  • @PSWorx said:

    But the Firefox zombie is still visible in the process list (second tab, as opposed to the applications list, first tab, which is really nothing more than a task bar with the "close this window" menu command duplicated as a button). The OT sounded as if the alleged VMWare process wouldn't be visible anywhere at all.

    Precisely - it didn't appear in the process list. The installer was essentially doing the PC equivalent of: "ps -aef | grep -i vmware", and wasn't smart enough to discount itself from the list, as in: ps -aef | grep -i vmware | grep -v install



  • A pid/lock file forgoten somewhere?


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.