forking new process when calling gnutls_global_init() function
h.habib at gmail.com
Tue Feb 19 14:05:53 CET 2008
Thanks for your response.
Actually in HPUX machine there is no /dev/random device and I think
thats why libgcrypt is forking a new process.
As per your suggestion I tried to install EGD but couldn't do so in
HPUX because it's showing some errors.
So one way of avoiding this is to kill the new process which has been created.
Can you pls let us know will there be any problem if we kill the new
process which is created.
On Feb 18, 2008 9:26 PM, Werner Koch <wk at gnupg.org> wrote:
> 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