Summary: base: remove use of SIGHUP to toggle INFO messages [#2923] Review request for Ticket(s): 2923 Peer Reviewer(s): Hans Pull request to: *** LIST THE PERSON WITH PUSH ACCESS HERE *** Affected branch(es): develop Development branch: ticket-2923 Base revision: c1a5a9d9353fd45152ec7604d7133361dd243614 Personal repository: git://git.code.sf.net/u/userid-2226215/review
-------------------------------- Impacted area Impact y/n -------------------------------- Docs n Build system n RPM/packaging n Configuration files n Startup scripts n SAF services n OpenSAF services y Core libraries n Samples n Tests n Other n Comments (indicate scope for each "y" above): --------------------------------------------- revision 093496e7869f7dc205ec9f176d5be30d75564c34 Author: Gary Lee <gary....@dektech.com.au> Date: Tue, 18 Sep 2018 08:05:40 +0000 fmd: enable reload of configuration without restart [#2923] Only FMS_PROMOTE_ACTIVE_TIMER, FMS_NODE_ISOLATION_TIMEOUT and FMS_ACTIVATION_SUPERVISION_TIMER are currently supported. These values can be changed in fmd.conf and take effect by sending SIGHUP to fmd. revision 712b275b16d4fe0c970c9bdac9828c7f894d22ae Author: Gary Lee <gary....@dektech.com.au> Date: Tue, 18 Sep 2018 08:05:40 +0000 base: add config file reader [#2923] Some configuration attribute are read by OpenSAF daemons as environment variables. eg. export FMS_PROMOTE_ACTIVE_TIMER=0 There is no easy way to reload these values without a restart. ConfigFileReader will parse these files looking for 'export VAR=VAL' and store them into a map, so a daemon can reload configuration without a restart. revision e759ff6ea285401a3bf152a0f4ebd271a38092aa Author: Gary Lee <gary....@dektech.com.au> Date: Tue, 18 Sep 2018 08:05:40 +0000 base: remove use of SIGHUP to toggle INFO messages [#2923] We need to use SIGHUP for reload of configuration Added Files: ------------ 0002-base-add-config-file-reader-2923.patch-+++ Complete diffstat: ------------------ src/base/Makefile.am | 2 ++ src/base/config_file_reader.cc | 43 ++++++++++++++++++++++++++ src/base/config_file_reader.h | 30 ++++++++++++++++++ src/base/logtrace.cc | 22 ------------- src/fm/fmd/fm_cb.h | 2 ++ src/fm/fmd/fm_main.cc | 70 ++++++++++++++++++++++++++++++++++++++++-- src/fm/fmd/osaf-fmd.in | 1 + 7 files changed, 146 insertions(+), 24 deletions(-) Testing Commands: ----------------- *** LIST THE COMMAND LINE TOOLS/STEPS TO TEST YOUR CHANGES *** Testing, Expected Results: -------------------------- *** PASTE COMMAND OUTPUTS / TEST RESULTS *** Conditions of Submission: ------------------------- *** HOW MANY DAYS BEFORE PUSHING, CONSENSUS ETC *** Arch Built Started Linux distro ------------------------------------------- mips n n mips64 n n x86 n n x86_64 y y powerpc n n powerpc64 n n Reviewer Checklist: ------------------- [Submitters: make sure that your review doesn't trigger any checkmarks!] Your checkin has not passed review because (see checked entries): ___ Your RR template is generally incomplete; it has too many blank entries that need proper data filled in. ___ You have failed to nominate the proper persons for review and push. ___ Your patches do not have proper short+long header ___ You have grammar/spelling in your header that is unacceptable. ___ You have exceeded a sensible line length in your headers/comments/text. ___ You have failed to put in a proper Trac Ticket # into your commits. ___ You have incorrectly put/left internal data in your comments/files (i.e. internal bug tracking tool IDs, product names etc) ___ You have not given any evidence of testing beyond basic build tests. Demonstrate some level of runtime or other sanity testing. ___ You have ^M present in some of your files. These have to be removed. ___ You have needlessly changed whitespace or added whitespace crimes like trailing spaces, or spaces before tabs. ___ You have mixed real technical changes with whitespace and other cosmetic code cleanup changes. These have to be separate commits. ___ You need to refactor your submission into logical chunks; there is too much content into a single commit. ___ You have extraneous garbage in your review (merge commits etc) ___ You have giant attachments which should never have been sent; Instead you should place your content in a public tree to be pulled. ___ You have too many commits attached to an e-mail; resend as threaded commits, or place in a public tree for a pull. ___ You have resent this content multiple times without a clear indication of what has changed between each re-send. ___ You have failed to adequately and individually address all of the comments and change requests that were proposed in the initial review. ___ You have a misconfigured ~/.gitconfig file (i.e. user.name, user.email etc) ___ Your computer have a badly configured date and time; confusing the the threaded patch review. ___ Your changes affect IPC mechanism, and you don't present any results for in-service upgradability test. ___ Your changes affect user manual and documentation, your patch series do not contain the patch that updates the Doxygen manual. _______________________________________________ Opensaf-devel mailing list Opensaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-devel