-Original Message-
From: Anders Widell [mailto:anders.wid...@ericsson.com]
Sent: Monday, October 07, 2013 5:58 PM
To: Mathivanan Naickan Palanivelu; Hans Feldt
Cc: opensaf-devel@lists.sourceforge.net
Subject: Re: [PATCH 1 of 1] opensaf: change daemon_exit to call exit() [#581]
I
Ack from me.
I guess we should also go through the code and make sure we follow this
rule from the Google C++ Style guide:
Static and Global Variables
Static or global variables of class type are forbidden: they cause
hard-to-find bugs due to indeterminate order of construction and
: Anders Widell [mailto:anders.wid...@ericsson.com]
Sent: den 9 oktober 2013 15:52
To: Hans Feldt; mathi.naic...@oracle.com
Cc: opensaf-devel@lists.sourceforge.net
Subject: Re: [devel] [PATCH 1 of 1] opensaf: change daemon_exit to call
exit() [#581]
Ack from me.
I guess we should also go
Widell; Hans Feldt; mathi.naic...@oracle.com
Cc: opensaf-devel@lists.sourceforge.net
Subject: RE: [devel] [PATCH 1 of 1] opensaf: change daemon_exit to call exit()
[#581]
Played with exit?
Are you referring to the episode with illegal stuff in the signal handler ?
/AndersBj
-Original Message
osaf/libs/core/common/daemon.c | 9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
By calling exit() instead of _Exit() registered exit functions are called. This
enabled for example flushing of gcov data.
diff --git a/osaf/libs/core/common/daemon.c
