psKill is effective, but it has one problem: If you have any custom scoped variables that you want to have persist in memory, they will revert back to the saved versions of the same variables from the previous time that Witango was stopped normally. If you use psKill, be sure to rebuild all of your custom scoped non-expiring variables on startup.
Bill On Tue, Jan 27, 2009 at 10:53 AM, Steve Briggs <[email protected]> wrote: > The easiest way I've found is to install PsKill and use the command: > > pskill -t witango.exe > > There is a Microsoft article on PsKill here: > http://technet.microsoft.com/en-us/sysinternals/bb896683.aspx > > -- Steve > > > > > On Jan 27, 2009, at 7:10 AM, Ted Wolfley wrote: > > Hi, > > I have a crontab on a Windows 2003 server that restarts the Witango service > every morning at 12 am. Occasionally the Witango service hangs while > shutting down and I have to restart the server. I'm thinking the cause is > the open connections to Witango and Witango is trying to close them. Is > there a way to drop all the connections before restarting the Witango > service? > > > Ted Wolfley > Lead Internet and Database Programmer > The Ogden Group of Rochester > phone: (585) 321 1060 x23 > fax: (585) 321 0043 > [email protected] > > www.ogdengroup.com > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > ************************************************** > Steve Briggs > Wow Pages > Portland, Maine > Houston, Texas > > 207-761-2450 > 888-325-5907 > > [email protected] > > ************************************************** > > > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
