Re: setsockopt(SO_REUSEADDR) (Re: Call for porting reports)

Yes, if
#define ONLY_REUSE_INET_SOCKETS
is included in solaris_sparc.h as in sco.h the postmaster can be started.

But except the libpq++, inet_aton() and SO_REUSEADDR problems there are more
problems:

1) psql cannot be made since perl is used to generate sql_help.h. There is
no perl on this machine. So configure doesn't help if perl is used anyway.

2) After I have copied sql_help.h from another platforms I could build psql,
but not start:

psql: PQconnectPoll() --  couldn't send startup packet: errno=22
Invalid argument

TCP/IP or Unix domain sockets doesn't matter.

Regards,
Andreas Kardos

-----Ursprüngliche Nachricht-----
Von: Tom Lane <tgl@sss.pgh.pa.us>
An: Kardos, Dr. Andreas <kardos@repas-aeg.de>
Cc: <hackers@postgresql.org>; <pgsql-ports@postgresql.org>
Gesendet: Dienstag, 11. April 2000 16:40
Betreff: setsockopt(SO_REUSEADDR) (Re: Call for porting reports)


> "Kardos, Dr. Andreas" <kardos@repas-aeg.de> writes:
> > SunOS 5.4 (sparc-sun-solaris) with native Sun compilers:
> > 3) The postmaster cannot be started:
>
> > sun2$ postmaster -i
> > FATAL: StreamServerPort: setsockopt(SO_REUSEADDR) failed: Protocol error
> > /usr/local/pgsql/bin/postmaster: cannot create UNIX stream port
>
> > Does SunOS not support Unix domain sockets? The same error appears
without
> > the -i option.
>
> There is an
> #ifdef ONLY_REUSE_INET_SOCKETS
> check to skip that call, but the symbol only seems to be defined for
> sco.  Now we see that Solaris doesn't like that call either.
>
> At the time the SCO patch was proposed, I thought we should just
> unconditionally skip the setsockopt(SO_REUSEADDR) call for the Unix-
> domain socket, because AFAIK it doesn't mean anything for that domain
> anyway.  Can anyone think of a reason not to do so now?  Seems to me
> that trying to apply a nonapplicable option is just asking for trouble.
>
> regards, tom lane
>