On 12/04/2013 02:00 PM, mathi.naic...@oracle.com wrote:
opensaf.spec.in | 1 +
osaf/services/saf/clmsv/config/Makefile.am | 3 +-
osaf/services/saf/clmsv/config/clmna.conf| 14 ++
And I forgot, please move clmna or whatever it will be called before immnd
Yeah, we could have a renaming ceremony in 4.5, but Today I just left it to be
termed as clmna(with recovery as node failfast),
because handle management is still with CLMServer.
Sure, I should change the binary name
The IMMSV_NUM_NODES and IMMSV_MAX_WAIT are just heuristic parameters with the
goal of having
a significant subset of the intended cluster participate in loading. Nodes that
dont come up
In time to participate in loading have to be synced after loading, which can
increase the
Time it takes for
Hi,
Can we have this pushed asap?
It will only add to hardening of opensaf.
Thanks,
Hans
On 12/09/2013 12:44 PM, Anders Widell wrote:
Summary: build: Add extra GCC hardening compilation flags [#650]
Review request for Trac Ticket(s): 650
Peer Reviewer(s): Mathi
Summary: FILL ME
Review request for Trac Ticket(s): 658
Peer Reviewer(s): Anders Widell
Pull request to: LIST THE PERSON WITH PUSH ACCESS HERE
Affected branch(es): LIST ALL AFFECTED BRANCH(ES)
Development branch: IF ANY GIVE THE REPO URL
Impacted area Impact
Ack.
Maybe you could consider if it makes sense to do the following
improvement, though:
Log to syslog ONCE until the error goes away. This could be done for all
values of errno (execpt EAGAIN and EINTR) by introducing a flag. When
write fails, log to syslog once and set the flag. Don't log
The page is explaining more about the order of these flags.
My interest in this page was more to do with the order in which
these flags would get 'applied' on to the AM_**flags (and not in the context of
C or C++!!)
Basically wanted to be sure of any further chance of 'overwriding' of these
saVersion=1 would be better
adding 4.0.0 was a mistake I did
Wel, 4.0.0 is still can-be considered as a baseline version!
I suggest let's leave it at 4.0.0 itself, and increment everybody in the next
release
Or probably increment everybody in this release itself?!( I remember that is how
We
