Summary: dtm: flush logtrace asap when logtrace owner is terminated [#3106] Review request for Ticket(s): 3106 Peer Reviewer(s): Minh, Gary Pull request to: *** LIST THE PERSON WITH PUSH ACCESS HERE *** Affected branch(es): develop Development branch: ticket-3106 Base revision: 5fe2c27d116770696710468c0ef3c88cf342a894 Personal repository: git://git.code.sf.net/u/winhvu/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): --------------------------------------------- *** EXPLAIN/COMMENT THE PATCH SERIES HERE *** revision c0017b9a45f49468a60fc493eae2d62c60b3958a Author: Vu Minh Nguyen <vu.m.ngu...@dektech.com.au> Date: Fri, 25 Oct 2019 15:19:59 +0700 dtm: flush logtrace asap when logtrace owner is terminated [#3106] To avoid the risk of losing traces, logtrace server should flush traces as soon as possible when logtrace owner is terminated. This patch also refactors LogServer::Run(). Complete diffstat: ------------------ src/dtm/transport/log_server.cc | 123 +++++++++++++++++++++++++--------------- src/dtm/transport/log_server.h | 7 +++ 2 files changed, 83 insertions(+), 47 deletions(-) Testing Commands: ----------------- - Enable trace e.g. pkill -USR2 osafimmnd - Flush the trace e.g. osaflog --flush osafimmnd - Open the trace file e.g. tail -f /var/log/opensaf/osafimmnd - Terminate logtrace owner e.g. pkill osafimmnd Testing, Expected Results: -------------------------- Check if the trace is flushed almost immediately after killing logtrace owner process. Conditions of Submission: ------------------------- Ack from reviewers 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 ~/.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