From owner-freebsd-questions Sat Oct 27 6:54:35 2001 Delivered-To: freebsd-questions@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 9ADF737B405 for ; Sat, 27 Oct 2001 06:54:30 -0700 (PDT) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Sat, 27 Oct 2001 14:54:26 +0100 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 15xTuK-0002sE-00; Sat, 27 Oct 2001 14:53:52 +0100 Date: Sat, 27 Oct 2001 14:53:52 +0100 (BST) From: Jan Grant X-X-Sender: To: Alexander-Jase Davidson Cc: FreeBSD Question Subject: Re: ntalkd fail to run [socket problem?] In-Reply-To: <00cd01c15ee5$0d4daa80$0100a8c0@K.Leung> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 28 Oct 2001, Alexander-Jase Davidson wrote: > Hi folks, > > I have just installed a copy of 4.4-release and as I use talk, it reported > "checking invitation on caller's machine". I have enabled ntalkd in > inetd.conf and of course, enabled inetd as well. I login as root and run > /usr/libexec/ntalkd and it reported something like "...socket on > non-socket". Since I have done some modification to the system afterwards as > an attempt to ressolve the problem, I messed up the machine and can not > remember the exact report. But it is something to do with socket. What can I > do? If ntalkd is anything like talkd (?) then it needs to be run from inetd; enable the line in /etc/inetd.conf for ntalkd. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk Theoremhood is positively decidable. It just takes time at least exponential in the length of the proof. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message