On Wed, Sep 16, 2009 at 8:02 AM, Ed Leafe <[email protected]> wrote: > On Sep 16, 2009, at 7:53 AM, Stephen Russell wrote: > >> The killing was not completing within the app itself. The idea of >> killing FF at that point by using the close button = #FAIL. Using >> another tool to "clean that up" like Task Info or process.exe would >> NOT be able to terminate FF. I would say that the app and not the OS >> were at fault, YMMV. If you tried to restart FF it said that the >> other one was running and you could NOT start a new one. FF was >> broken at that point. > > > It's at times like these that I appreciate my Mac/Linux boxes, where > a simple 'killall Firefox' does just that, and I can go back to > getting work done. ------------------------------
I thought that I had that via process.exe. I have a WAG that FF was interacting with other threads in the OS and they were cocked up. I wish mine kill process worked!!! -- Stephen Russell Sr. Production Systems Programmer SQL Server DBA Web and Winform Development Independent Contractor Memphis TN 901.246-0159 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
