From: blt@comlab.ox.ac.uk (Brian Thompson) Subject: Net-2 problems with ftpd and telnetd Date: Tue, 29 Jun 1993 22:30:23 GMT
I can telnet out and ftp out fine to other hosts, but on trying to telnet
or ftp to my own machine either via loopback or from another system there
are problems.
I think the problem is relevant to trying to start the telnetd and ftpd
daemons. inetd doesn't report errors, but ps shows that they definitely
*don't* start. Running them manually doesn't work: ftpd simply doesnt
start and prints nothing to give any clue as to why not, and telnetd
bombs with an error message:
telnetd: getpeername: bad file number
What does getpeername() actually do? Looking at the sources for telnetd
the above error results from getpeername(0, ..., ...). The latter parameters
seem reasonable, but the 0 is supposed to be the file descriptor of the
socket, according to the source for getpeername in the kernel. Surely this
is duff code?
A whole other problem is that try as I might, I can't get any of the net-2
stuff to recompile. My gcc definitely isn't broken - I can recompile the
kernel without any problems. The sort of errors indicate that the sources
date back from a time long before pl10, and the headers no longer agree.
There are lots of type violations reported.
Surely someone else can succesfully telnet into their machine? Surely someone
else has had this same problem? Help!
Brian Thompson