Re: Orphaned sql turbo processes.

> In article <pduttaCw9xvu.8y5@netcom.com>, > Partha Dutta <pdutta@netcom.com> wrote: > >Jonathan Leffler (johnl@informix.com) wrote: > >: >From: shyam@minerva.robadome.com (Shyam Davuburu) > > Stuff deleted... > > While we're on the subject... > At my current job all the programmers were told to never, ever kill > a sqlturbo process, but to get the DBA to do it. I, of course, totally > ignore this policy when I need to bail out of a long querey. I use kill > -15.There seems to be some concern that if you are doing an update to the > Informix database and you do a kill -15 on the process, that sqlturbo > will not clean up any locks. I always assumed it was smart enough to > cleanup after itself as long as you didn't do a kill -9. > Does anyone out there confer or am I off base? No and yes respectively. You could leave all sorts of locks lying about if you kill a sqlturbo and you may make a pretty good job of fouling up the logical logs if you're unlucky. You'd then have to kick off all your users while you stop and re-start OnLine. Yeugh. *Always* use tbmode -z. Thank goodness kill isn't so much as applicable with DSA (ie. 6.00-on). The idea of the sqlturbo process no longer exists and you *have* to use onmode -z. akent@cix.compulink.co.uk (Andy Kent) -------------------------------------