From owner-freebsd-questions Tue Feb 20 10:22:14 2001 Delivered-To: freebsd-questions@freebsd.org Received: from trinity.lee.net (trinity.lee.net [208.229.121.1]) by hub.freebsd.org (Postfix) with ESMTP id AADA437B6D1 for ; Tue, 20 Feb 2001 10:22:07 -0800 (PST) (envelope-from awells@journalstar.com) Received: from journalstar.com (leepcD-096.sub-d.lee.net [208.205.127.96]) by trinity.lee.net (8.9.3/8.9.3) with ESMTP id MAA16330; Tue, 20 Feb 2001 12:22:00 -0600 Message-ID: <3A92B5AA.7AEDC3D1@journalstar.com> Date: Tue, 20 Feb 2001 12:21:30 -0600 From: Tony Wells X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: slamdunk Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Cant get ftpd's started - Help References: <4.3.2.7.2.20010218020924.02845e60@127.0.0.1> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG slamdunk wrote: > > Having sorted out my strange, unkillable login on my box (by a reboot) I > now have a different problem. I run 2 ftp daemons, average common or garden > freebsd supplied ftpd and a copy of glftpd on a seperate port. > > Since the reboot I cant see the either running and any attempt to ftp in > using either of the ports produces a "connection refused" error > > Trying to start them manually generates these errors:- > ftpd[838]: getpeername (ftpd): Socket operation on non-socket > glftpd: getpeername (/caddy/ftp/bin/glftpd): Socket operation on non-socket > > There is nothing in the messages file to indicate failure of launching them > from inetd.conf, the entries in there are as follows:- > ftp stream tcp nowait root /usr/libexec/ftpd ftpd -l > glftpd stream tcp nowait root /caddy/ftp/bin/glftpd -l -o -i ----^ I'm not sure what inetd will think if this entry since glftpd is not a "well known service" according to the inetd man page. (It doesn't exist in /etc/services.) You could probably add a line in /etc/services to whatever port glftpd is listening to, taking care not to use a port already assigned to another "well known service." > > As far as I am aware nothing much has changed to my configuration, and I am > totally at a loss, as another reboot has not solved it either. > > Can anyone give me any pointers? > > Jerry > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message