From owner-freebsd-questions@FreeBSD.ORG Wed Jul 23 00:48:04 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5BE037B401 for ; Wed, 23 Jul 2003 00:48:04 -0700 (PDT) Received: from stormdbn.stormnet.co.za (stormdbn.stormnet.co.za [196.22.196.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDAFC43FAF for ; Wed, 23 Jul 2003 00:48:03 -0700 (PDT) (envelope-from nelis@brabys.co.za) Received: from postoffice.brabys.co.za ([192.96.48.13] helo=brabys.co.za) by stormdbn.stormnet.co.za with esmtp (Exim 4.20) id 19fELx-0008S0-4L for questions@freebsd.org; Wed, 23 Jul 2003 09:48:01 +0200 Received: from [192.96.48.37] (nelis [192.96.48.37]) by brabys.co.za (8.12.0/8.12.0) with ESMTP id h6N7leEU009363 for ; Wed, 23 Jul 2003 09:47:40 +0200 From: Nelis Lamprecht To: FreeBSD Questions Mail List Content-Type: text/plain Organization: Message-Id: <1058946460.455.347.camel@enigma.8ball.co.za> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 23 Jul 2003 09:47:40 +0200 Content-Transfer-Encoding: 7bit X-MailScanner: Found to be clean Subject: Re: tftpd startup - solved X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: nelis@brabys.co.za List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2003 07:48:05 -0000 Solved this one on my own. If I'd bothered to test using the tftp client I would have noticed it was actually was running. Due to the fact it doesn't show as a process I'd just assumed it wasn't running forgetting it falls under inetd. Sorry for the question :) Nelis -----Forwarded Message----- > From: Nelis Lamprecht > To: FreeBSD Questions Mail List > Subject: tftpd startup > Date: 23 Jul 2003 08:52:48 +0200 > > Hi, > > I'm trying to get tftpd running ( FreeBSD 4.7 ) and I keep getting this > error message in syslog: > > tftpd[82755]: recvfrom: Socket operation on non-socket > > This leads me to my next question which is, is there a way to startup > inetd from the command line because I'm almost sure the above error is > related. I have made the necessary changes to /etc/inetd.conf > > Kind regards, > Nelis