[collectd] Ohhhh jeeee, libgcrypt 1.4.1 + collectd 4.7.2
Luke Heberling
collectd at c-ware.com
Mon Aug 31 19:31:30 CEST 2009
On Monday 31 August 2009 09:03:37 Sebastian Harl wrote:
> Hrm … from a quick look at the libcrypt documentation I suppose we need
> to call gcry_control() using the 'GCRYCTL_INIT_SECMEM' command to
> explicitly initialize the secure memory. Sounds like this was required
> in libgcrypt 1.4.1 but is handled automatically in later versions.
>
also looks like there's some special initialization necessary for threads. I
doubt that this is handled by the new default behavior in 1.4.4. Don't know
that it's truly necessary if the network plugin is the only plugin using
gcrypt.
Here's a patch that works for me with 1.4.1.
I followed an example for pthread initialization and initialized gcry to 32k,
only since that's apparently the default that's used in 1.4.3. I did it in
network.c's module_register function. Kind of an abuse, I know.
Luke Heberling
-------------- next part --------------
A non-text attachment was scrubbed...
Name: network.diff
Type: text/x-patch
Size: 786 bytes
Desc: not available
Url : http://mailman.verplant.org/pipermail/collectd/attachments/20090831/4358a71b/attachment.bin
More information about the collectd
mailing list