Summary: log: fix ER in syslog if changing saLogStreamFileName and other atrributes[#1887] Review request for Trac Ticket(s): #1887 Peer Reviewer(s): Vu, Mahesh, Lennart Pull request to: Vu Affected branch(es): 4.7.x, 5.0.x, default Development branch: default
-------------------------------- Impacted area Impact y/n -------------------------------- Docs n Build system n RPM/packaging n Configuration files n Startup scripts n SAF services y OpenSAF services n Core libraries n Samples n Tests n Other n Comments (indicate scope for each "y" above): --------------------------------------------- <<EXPLAIN/COMMENT THE PATCH SERIES HERE>> changeset 17eedafb8a4d9df8fe145f48dc4b9278dd8a1214 Author: Canh Van Truong <canh.v.tru...@dektech.com.au> Date: Thu, 04 Aug 2016 10:12:13 +0700 log: fix ER in syslog if changing saLogStreamFileName and other atrributes[#1887] When changing saLogStreamFileName with other attributes, the action "closing current log file", "rename", "create new cfg and log file" are duplicated. This cause the ER in syslog, because lgsv can not find log file when closing secondly. Name of current log file was changed at first time. This patch make lgsv just do above action only once. Complete diffstat: ------------------ osaf/services/saf/logsv/lgs/lgs_imm.cc | 52 ++++++++++++++++++++++++++-------------------------- 1 files changed, 26 insertions(+), 26 deletions(-) Testing Commands: ----------------- Maunual test: 1/ Change saLogStreamFileName together with other attribute immcfg safLgStrCfg=saLogAlarm,safApp=safLogService -a saLogStreamFixedLogRecordSize=150 -a saLogStreamFileName=alarmname 2/ Check no ER in syslog (or messages file) Check new cfg and log file in saflog folder Testing, Expected Results: -------------------------- - Command when changing attributes in step 1 successfull - No ER in syslog and new cfg, log file was created. 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 n n 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 ~/.hgrc file (i.e. username, 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