Re: 2.4.0-test6 network socket problems

2000-10-14 Thread J. Scott Kasten
Thanks Allen, you're exactly right. I'm charged with the task of finding lots of nasties like that in our old code base where a number of things were just hacked in down and dirty. Our embeded environment moved from XINU on an SH2/SH3 with no mmu support and a BSD protocol stack we hacked in ou

Re: 2.4.0-test6 network socket problems

2000-10-13 Thread Alan Cox
> I've found the problem. This type of loop does not work: > > do { > alarm(t); > read(fd); > if (EINT) >exception(); > else >alarm(0); > } while (data); > > There are some semantics here that differ from other *nix where this > works. The read() won't come out

Re: 2.4.0-test6 network socket problems

2000-10-13 Thread Richard B. Johnson
On Fri, 13 Oct 2000, J. Scott Kasten wrote: > I've found the problem. This type of loop does not work: > > do { > alarm(t); > read(fd); > if (EINT) >exception(); > else >alarm(0); > } while (data); > > There are some semantics here that differ from other *nix wh

Re: 2.4.0-test6 network socket problems

2000-10-13 Thread J. Scott Kasten
I've found the problem. This type of loop does not work: do { alarm(t); read(fd); if (EINT) exception(); else alarm(0); } while (data); There are some semantics here that differ from other *nix where this works. The read() won't come out when the alarm comes, and