I know this is a little off topic, but can anyone point me to some good
reference material for thread handling on Unix?  Up till recently, I've done
nearly all my coding under Win32.  I've ported over most of my code base to
linux, but I have a gaping hole where threads are concerned.

Mostly I'm curious if there is a thread local storage equivalent in Unix
land.

Just email me, and save the board some spam.

Thanks... and sorry for being off topic.

Andy

----- Original Message -----
From: Amit Chopra <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 06, 2000 1:08 AM
Subject: Re: thread support and Memory leaks


> Hi,
>
> > 2- thread support: do we have to explicitly call
> > CRYPTO_set_locking_callback and CRYPTO_set_id_callback in a
multithreaded
> > context?
> Yes, if your application is multi-threaded you have to set the callbacks.
>
> >It is said so in the "threads" manpage, but they seem to be used
> > only in test programs (mttest.c, th-lock.c)
> Because other example applications are not multi-threaded.
>
> > 3-  I am calling   ERR_remove_state(0) at the end of each thread; any
> > other cleanup function to call?
> I don't think you need to do much else.
> To de-init the library as a whole I also do an ERR_free_strings()
> and EVP_cleanup() before my application exits. This works for me.
>
> Good Luck,
> Amit.
> ______________________________________________________________________
> OpenSSL Project                                 http://www.openssl.org
> User Support Mailing List                    [EMAIL PROTECTED]
> Automated List Manager                           [EMAIL PROTECTED]


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to