humkum opened a new pull request #401:
URL: https://github.com/apache/rocketmq-client-cpp/pull/401


   …main project
   
   ## What is the purpose of the change
   
   #400
   
   ## Brief changelog
   
   Add the log path to the environment variable by using setenv function, and 
set this path before the log object is initialized.
   
   ## Verifying this change
   
   By setting producer log path to "/logs/producer/cpp/", the log file was 
saved in "~/logs/producer/cpp/", and the main log file name is 
"rocketmq_client.log", backup log file name's format is 
"rocketmq_client_%Y%m%d-%N.log". As follows:
   
   
![image](https://user-images.githubusercontent.com/50660789/152913249-fbde5f35-fd13-4c79-b260-50eceb30a85e.png)
   
   
   Follow this checklist to help us incorporate your contribution quickly and 
easily. Notice, `it would be helpful if you could finish the following 5 
checklist(the last one is not necessary)before request the community to review 
your PR`.
   
   - [x] Make sure there is a [Github 
issue](https://github.com/apache/rocketmq/issues) filed for the change (usually 
before you start working on it). Trivial changes like typos do not require a 
Github issue. Your pull request should address just this issue, without pulling 
in other changes - one PR resolves one issue. 
   - [x] Format the pull request title like `[ISSUE #123] Fix UnknownException 
when host config not exist`. Each commit in the pull request should have a 
meaningful subject line and body.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Write necessary unit-test(over 80% coverage) to verify your logic 
correction, more mock a little better when a cross-module dependency exists.
   - [ ] If this contribution is large, please file an [Apache Individual 
Contributor License Agreement](http://www.apache.org/licenses/#clas).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to