On 02/10/2013 08:09, Seth Arnold wrote:
> Are you confident about multi-threading? I don't see any linker commands
> to link against the threading libraries in our build logs:
> https://launchpadlibrarian.net/92810645/buildlog_ubuntu-precise-amd64
> .cyrus-sasl2_2.1.25.dfsg1-3_BUILDING.txt.gz and I also see extensive
> use of fork(2) in the upstream git: http://git.cyrusimap.org/cyrus-
> sasl/tree/saslauthd/saslauthd-
> main.c?id=dedad73e5e7a75d01a5f3d5a6702ab8ccd2ff40d
>
>>From just the five minutes I've looked, I'd say it looks like usual
> Unix-style preforking server, not threaded server.
>
Hi
I'm not an expert on this. But when compiled with --with-ipctype=doors
it will use pthreads. Also, the auth_shadow.c contains #ifdef _REENTRANT
directives, suggesting possible multi-threaded use.
So someone (perhaps upstream) should make sure the code is safe to use
in all configurations.
On 02/10/2013 08:09, Seth Arnold wrote: /launchpadlibra rian.net/ 92810645/ buildlog_ ubuntu- precise- amd64 sasl2_2. 1.25.dfsg1- 3_BUILDING. txt.gz and I also see extensive git.cyrusimap. org/cyrus- saslauthd/ saslauthd- id=dedad73e5e7a 75d01a5f3d5a670 2ab8ccd2ff40d
> Are you confident about multi-threading? I don't see any linker commands
> to link against the threading libraries in our build logs:
> https:/
> .cyrus-
> use of fork(2) in the upstream git: http://
> sasl/tree/
> main.c?
>
>>From just the five minutes I've looked, I'd say it looks like usual
> Unix-style preforking server, not threaded server.
>
Hi
I'm not an expert on this. But when compiled with --with- ipctype= doors
it will use pthreads. Also, the auth_shadow.c contains #ifdef _REENTRANT
directives, suggesting possible multi-threaded use.
So someone (perhaps upstream) should make sure the code is safe to use
in all configurations.
CU,
Arno