[24337] in Kerberos
Re: Assertion failuers
daemon@ATHENA.MIT.EDU (fariba)
Mon Jul 25 23:01:13 2005
Date: Mon, 25 Jul 2005 20:01:49 -0700
From: fariba <fariba@usc.edu>
In-reply-to: <42D30D3B.8020404@usc.edu>
To: Phil Dibowitz <phil@usc.edu>
Message-id: <42E5A79D.7020203@usc.edu>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
cc: Sam Hartman <hartmans@mit.edu>
cc: Toan Nguyen <toan@usc.edu>
cc: Ken Raeburn <raeburn@mit.edu>
cc: kerberos@mit.edu
Errors-To: kerberos-bounces@mit.edu
seems like it worked. we have not been getting dead mureqds for a
while(this is our application that was failing)
fariba wrote:
> i relinked our other application(mureqd) with the new 2.6 (thread
> disabled) and released it, to see if the process functions better now.
>
> Phil Dibowitz wrote:
>
>> On Sun, Jul 10, 2005 at 03:53:40PM -0400, Sam Hartman wrote:
>>
>>
>>>>>>>> "fariba" == fariba <fariba@usc.edu> writes:
>>>>>>>>
>>>>>>>
>>> fariba> i work with phil as well. i was wondering what are the
>>> fariba> proc/con of using these flags:
>>>
>>> fariba> --disable-shared --enable-static --disable-threads
>>>
>>> It turns off threads support which gets you roughly the 1.3.x
>>> behavior. If miltiple threads are using the library at once you can
>>> run into problems. It disables shared libraries and enables static
>>> libraries. That means that Kerberos is linked into each application
>>> instead of using a dynamic library.
>>>
>>
>>
>> BTW, I didn't disable shared libraries (we need them), but I did disable
>> threads.
>>
>>
>>
>
> ________________________________________________
> Kerberos mailing list Kerberos@mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
