Re: Orphaned sqlexec daemons

> When a user has to reboot his PC for any of a myriad of reasons unrelated > to our app a sqlexec daemon is left orphaned on the unix server. > We are using TCP/IP as our transport. It is important for us > to be able to identify and terminate such processes, or better, > have them terminate themselves. > > Anyone know of a way? If it involves tweaking TCP/IP parameters, > what is the impact of such changes on other tcp/ip processes? Back in the (golden?) olden days of 2.10.06 informix for dos, I had the same problem. I found that the DBPATH that you set on the pc was passed up to the server by Inet, and used as a command line arg to the sqlexec. As the engine was OnLine5, the DBPATH was unused, so I set it to the ethernet addr of the pc. The autoexec of the pc issued an rsh to the server to kick off a process to look for any offending sqlexec, and very carefully kill it (tbmode -z didn't work then either!). Be VERY careful, a badly timed kill -9 of an sqlexec will bring down the engine very quickly!! Good luck, Andy. -- =-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-= Andy Lennard andy@kontron.demon.co.uk =-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=-~-=