🚀 go-pugleaf

It's almost 1 year ago since several people have noticed, that Sybase would  
eventually crash the NeXT. It happened always after about 1000 logins into  
the server. I had some discussion with 'ask_next' and it came out, that it  
was a bug in NeXT-networking software. Anyway, nobody at NeXT could give a  
solution, so I waited for 3.0. Now, running the crash program showed the  
same behaviour: after 1000 logins the NeXT would come to a complete stop. 

Because several people have reported this bug, it is not understandable,  
nor acceptable that the responsible people at Next didn't care about it at  
all, even if I had given them my short program which verified the crash.  

Because the DB-Kit is one of the big improvements of 3.0, it's a mjor  
annoyance. Today I have tried again to find out what happens. And the  
solution is so simple:

Sybase (in the standard installation) uses port numbers 3696 and 4696 for  
communication with the server. NeXT internally assignes portnumbers  
1024-5000. This is standard BSD behaviour, btw.

And a 'netstat' just before crash-time showed: The NeXT tries to assign the  
same port Sybase is using !

So after changing the Sybase-installation to use portnumbers greater than  
5000, everything worked fine !

So for every tcp/ip-User/Programmer:

	NEVER USE PORT-NUMBERS <= 5000 !

Perhabs this should become part of the FAQ !


-- 
------------------------------------------------------------------
Thomas Funke  ** E-mail: thf@zelator.in-berlin.de
NeXT-Developer * Unix-Consultant
------------------------------------------------------------------