We're using PL4 and we're on a Pentium 99 running Solaris.. And yes, it
does cause a problem.. Its rare, but everyonce and awhile the port will
get binded, the mud will freeze up, and we wont be able to kill the
process.. Of course, this is a threat somewhat to our stability..:)
God against man, man against God, man against nature, God against man, man
against God, man against nature, nature against man, nature against God,
God against nature...very funny religion!
On Sat, 25 Feb 1995, Jeremy Elson wrote:
>
> > The problem seems to be in the following function:
> >
> > #if defined(SO_LINGER)
> > {
> > struct linger ld;
> >
> > ld.l_onoff = 0;
> > ld.l_linger = 0;
> > if (setsockopt(s, SOL_SOCKET, SO_LINGER, &ld, sizeof(ld)) < 0) {
> > perror("setsockopt LINGER");
> > exit(1);
> > }
> > }
> > #endif
> >
> >
> > The warning is :
> >
> > passing arg 4 of 'setsockopt' from incompatiable pointer type
> >
> >
> > Whadda ya thing sirs?
>
> I think it would help if you told me which version of the code and which
> operating system you're using. :)
>
> I think that warning was fixed in pl5 but it shouldn't have been causing
> any problems in any case.
>
> -JE
>
This archive was generated by hypermail 2b30 : 12/07/00 PST