forking new process when calling gnutls_global_init() function
wk at gnupg.org
Mon Feb 18 16:56:14 CET 2008
On Mon, 18 Feb 2008 13:58, h.habib at gmail.com said:
> gnutls_global_init() function at the time of initialization of TLS a
> new process is forked printing following trace in console.
> [New process 28026]
> warning: reading `r3' register: No data
> Detaching after fork from process 28026
Frankly, I still don't understand the origin of this message. My
interpretation is that some process reads a register named r3 and
returns no data. Whatever this means. The entire output looks like a
system call trace utility - I don't know HPUX enough to tell.
> One more think the same code is running fine in LINUX OS without
> creating any new process.
Right. Thai is because it uses /dev/random. As stated when configuring
libgcrypt, you are better off running the EGD:
The performance of the Unix random gatherer module (rndunix) is not
very good and it does not keep the entropy pool over multiple
invocations of Libgcrypt base applications. The suggested way to
overcome this problem is to use the
Entropy Gathering Daemon (EGD)
which provides a entropy source for the whole system. It is written
in Perl and available at the GnuPG FTP servers. To enable EGD you
should rerun configure with the option "--enable-static-rnd=egd".
For more information consult the GnuPG webpages:
Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz.
More information about the Gcrypt-devel