Matthew Lye wrote:
> For a long time I've seen the following warning produced many, many
> times per session:
>
> > 09-05-12 22:01:00 (WARNING): getpeername() failed: Invalid argument
>
> I just got around to checking into it with dtrace, and it appears that
> getpeername() is not actually be
Matthew Lye wrote:
> On 12-May-09, at 11:26 PM, Christian Biere wrote:
> > If that's the case you should see the relevant warnings on stderr.
> > You can also try to remove the lines to verify your thesis.
>
> No, no, that would have been clever.
>
> It's more complicated than I thought. There's
On 12-May-09, at 11:26 PM, Christian Biere wrote:
> If that's the case you should see the relevant warnings on stderr.
> You can also try to remove the lines to verify your thesis.
No, no, that would have been clever.
It's more complicated than I thought. There's a "getpeername
$UNIX2003()", whi
Christian Biere wrote:
> Matthew Lye wrote:
> > For a long time I've seen the following warning produced many, many
> > times per session:
> >
> > > 09-05-12 22:01:00 (WARNING): getpeername() failed: Invalid argument
> >
> > I just got around to checking into it with dtrace, and it appears that
Matthew Lye wrote:
> For a long time I've seen the following warning produced many, many
> times per session:
>
> > 09-05-12 22:01:00 (WARNING): getpeername() failed: Invalid argument
>
> I just got around to checking into it with dtrace, and it appears that
> getpeername() is not actually be
This may be old news.
For a long time I've seen the following warning produced many, many
times per session:
> 09-05-12 22:01:00 (WARNING): getpeername() failed: Invalid argument
I just got around to checking into it with dtrace, and it appears that
getpeername() is not actually being called
