[3115] in Kerberos
Re: kerberos won't start
daemon@ATHENA.MIT.EDU (Prem Tirilok)
Fri Apr 15 15:39:28 1994
From: prem@lachman.com (Prem Tirilok)
To: jdy@judith.jpl.nasa.gov (Jimmie Young)
Date: Fri, 15 Apr 1994 14:22:49 -0500 (CDT)
Cc: kerberos@MIT.EDU
Reply-To: prem@lachman.com
In-Reply-To: <9404151801.AA08015@judith.Jpl.Nasa.Gov> from "Jimmie Young" at Apr 15, 94 11:01:24 am
Try the SO_REUSEADDR setsockopt option.
regards,
- Prem
According to Jimmie Young:
>
>
> We have seen this problem quite a bit - whether or not it's actually a problem
> in Kerberos or SunOS, we haven't determined. However, recent development in
> socket-based client/server applications that we have been doing lead us to
> believe the latter.
>
> What is apparently happening in these situations is that the system is not
> cleaning up the socket after Kerberos is terminated (whether explicitly through
> a kill or by shutting down the system) - hence when the system is resumed and
> Kerberos is told to start back up, the system thinks the socket is still in an
> "unbindable" state and refuses to perform the new bind. In these cases, if you
> perform a netstat -a, the Kerberos entry will still be listed even if the
> Kerberos server is not running.
>
> I myself have been trying to find a way by which the socket(s) can be cleaned
> up - particularly in light of developing c/s applications, many times the
> server needs to be re-started frequently and if the socket has not been cleaned
> up, I either have to wait (it eventually times out and cleans up, but this can
> be a LONG time - days even, depending on the state the socket/port was left in
> at the time of termination) or change the port number it's listening on and
> re-compile (very time consuming). If anyone knows of a way to "clean up the
> sockets/ports", please let me know, I'd greatly appreciate it.
>
> Jimmie Young
> MIPS Database Management Sub-system
> NASA/JPL
> jdy@judith.jpl.nasa.gov
>
