[942] in linux-net channel archive

home help back first fref pref prev next nref lref last post

Re: telnet/ftp/rlogin/rsh not working between Linux machines. (fwd)

daemon@ATHENA.MIT.EDU (Werner Almesberger)
Sun Aug 20 22:43:57 1995

From: Werner Almesberger <almesber@lrc.epfl.ch>
To: linux-net@vger.rutgers.edu
Date: Sun, 20 Aug 1995 23:06:54 +0200 (MET DST)

Matthias Urlichs <urlichs@smurf.noris.de> wrote:
> Besides, accepting and then immediately throwing away a connection is
> against quite a few RFCs. SMTP, FTP, NNTP, I can probably dig out a few
> others.  :-/

Normally, this is "should" behaviour. I haven't checked the RFCs you
mention, but they better don't disallow premature termination (crash,
out of memory, can't fork, system shutdown, etc.) of a demon/server
process ...

Arnt Gulbrandsen <agulbra@troll.no> wrote:
> But it can never reject the connection - by the time it's started the
> connection has been established.  inetd could, I think, if there's any
> way to getpeername() before one accepts the connection.

Hmm, besides the TCP timing issues, I could imagine how you would apply
getpeername (a listening socket has no peer, so that would be
unambiguous), however I have difficulties imagining how you'd reject the
call - you don't want to close the socket and anything else (shutdown,
setsockopt, ioctl, etc.) looks like requiring a big #ifdef linux ...

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, DI-LRC,EPFL,CH   werner.almesberger@lrc.di.epfl.ch /
/_IN_R_311__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/

home help back first fref pref prev next nref lref last post