Re: System freezes after "could not getpeername"

... ciao:
 
: on "8-30-2010" "Andreas Moroder" writ:

: but there seems to be a correlation between the getpeername call in inted and
: the freeze of the machine, so I prefer to avoid inetd in this case .
 
   i tend to think that solution cosmetic at best, and at worst, a 
misdirected effort.  my reading of the 'inetd' manpage does not suggest 
it calls 'getpeername', but insteat hands off connections to implied 
servers.  seems to me, 'getpeername' is more likely local to the 
answering server, that's just a quess though.

   "having" to bypass inetd, is expedient, but not an elegant solution.
 
    for my part, i'd start looking at bind ...


-- 
... it's not what you see ,
    but in stead , notice ...