[28070] in Kerberos
Re: kprop: Connection refused in call to connect while opening
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Thu Jul 19 23:24:48 2007
In-Reply-To: <cb25fa940707191933y7abd89cdo9247777975f01e45@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Message-Id: <A53BBD98-E98F-4305-BC9E-0A49F648D10D@mit.edu>
From: Ken Raeburn <raeburn@mit.edu>
Date: Thu, 19 Jul 2007 23:24:35 -0400
To: Le Trung Kien <aloneattack@gmail.com>
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On Jul 19, 2007, at 22:33, Le Trung Kien wrote:
> and the error :
>
> kprop: Connection refused in call to connect while opening
> connection to
> slave.ole.abc
>
> I have search google and found someone said that let "kpropd"
> running in
> slave KDC. But when I enter command "kpropd" on
> slave KDC, I got:
>
> # kpropd
> kpropd: getpeername: Socket operation on non-socket
>
> Please help.
Normally, the kpropd program expects to be started with its standard
input and output bound to the network connection from the master KDC,
as would happen if you started it from inetd. Reporting low-level
errors from attempting to apply socket functions to your terminal is
perhaps not the best way to remind you of this, I know. I've just
changed this to be a little more friendly in the 1.7 release:
$ ./kpropd
./kpropd: Standard input does not appear to be a network socket.
(Not run from inetd, and missing the -S option?)
$
You can either set up inetd.conf to run kpropd when connections come
in, or run kpropd in standalone mode with the -S option.
Ken
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
