Re: oninit failure

The quick way to get it restarted is to hash out the line in /etc/services = for the port id and add another. Informix will then restart immediately. If you are using Informix connectivity across machines you will need to = change the port id on all machines, but it does give you a quick restart = for the server concerned. I did some digging a couple of years back to see if there was a way to = free the port but it all got too complicated. Any 'C' programmers out = there like to have a go at it? rgds Peter Tashkoff <tashkop@iname.com> Zespri International Limited Std Disclaimers Apply All rights reserved. No party may use this document to vilify another. Zespri New Zealand Kiwifruit, The World's Finest >>> Paul Watson <watson@mcmail.com> 7/05/98 00:08:31 >>> Jo=E3o Carvalho wrote: >=20 > Hi all ! >=20 > There is a story that I would like to share: >=20 > After a system crash, in wich the server 'misterously' > stoped due to a still unknown problem, the oninit command > failled and was impossible to start online. The last error reported > in the log was 25572 (Network driver cannot bind a name to the port). >=20 [cutting] If the engine crashes it can leave the network connections still open (netstat -a) ie in a FINWAIT(2). When they close down, the time is dependent on the flavour of Unix, the engine will re-start. =20 --=20 Paul Watson # WF Software Ltd # If it ain't broke, =20 Tel: +44 1436 674729 # fix it till it is.=20 Fax: +44 1436 678693 #=20 www.wfsoftware.co.uk #