sockets for SYSV (UNIXPC)
Andrew Poling
ecf_hap at jhunix.HCF.JHU.EDU
Wed Mar 22 05:07:54 AEST 1989
In article <454 at polyof.UUCP> john at polyof.UUCP ( John Buck ) writes:
>If you get the UNIX PC WIN TCP package, you will get a BSD 4,2
>compatible library with it, including full sockets. Beware, though,
>they don't work exactly correct (IE the implementation is flawed;
>select doesnt work right, for one thing).
You mean it's not supposed to panic the system? :-) Actually, let me
temper that remark with specifics. I have run into problems with
select(3W) on numerous occasions. If you have too many long
selects(3W) active at once, it will overflow your timeout table ==>
PANIC.
My solution (based on intuition more than fact) has been to limit my
selects(3w) to one second. This does hurt my performance, since it
makes my machine impatient, but it allows me to run such goodies as
BIND, Sendmail5.58, and other resolver-based routines that I have
found SysV ports of here and there.
On the positive side, 4.2 BSD socket code usually runs out of the box
as soon as you fix all of the other SysV/BSD (ahem) problems.
As a side point - I noted in a bug report release for the 3.* code
for our 3b4000 warns of possile panics in (as I read it) much the
same way. I guess Wollongong only ports this stuff once, then
re-uses the same buggy code. :-(
Disclaimer: These are my own opinions - don't blame my employer -
they don't even know that I think. :-)
Andy
andy at gollum.hcf.jhu.edu
ecf_hap at jhunix.UUCP
ecf_hap at jhuvms.BITNET
More information about the Comp.sys.att
mailing list