Handling process termination
Hi All, I am using boost library for logger. Seems pretty good. Am using boost with asynchronous sink. Hence require a close down of sink explicitly. But this is not possible when process crashes. Do boost have any mechanism for the same (Like handling the signals of OS and like stack dumps)? What does boost prefer for unexpected termination of process where the logs will go out uncollected? Could you please help me out of this? Thanks and Regards Shaginesh PK ________________________________ Confidentiality Statement / Disclaimer : This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt. The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message. ________________________________
On 10.06.2016 06:44, Shaginesh P.K.(NeSTIT) wrote:
Hi All,
I am using boost library for logger. Seems pretty good.
Am using boost with *asynchronous sink*. Hence require a *close down of sink explicitly*. But this is not possible when process crashes.
Since when the process crashes everything within it goes away it's inherent to asynchronous sinks to have potential to loose some of the most recent logs. I don't see anything that could be done about it. The only way I can imagine to ensure that logs are guaranteed not to get lost is to use synchronous sink with some fast custom backend. Your backend could, for instance, forward logs via shared memory to some other process that actually does the writing to whichever persistent storage you choose to write to. But as far as I know there are no such off-the-shelf backends offered in Boost.Log. Cheers, Leon
Do boost have any mechanism for the same (Like handling the signals of OS and like stack dumps)?
What does boost prefer for unexpected termination of process where the logs will go out uncollected?
Could you please help me out of this?
Thanks and Regards
Shaginesh PK
------------------------------------------------------------------------
*Confidentiality Statement / Disclaimer* : This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt.
The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message.
------------------------------------------------------------------------
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Thank you. That's some input for me. Thanks and Regards Shaginesh PK From: Boost-users [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Leon Mlakar Sent: Friday, June 10, 2016 6:32 PM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Handling process termination On 10.06.2016 06:44, Shaginesh P.K.(NeSTIT) wrote: Hi All, I am using boost library for logger. Seems pretty good. Am using boost with asynchronous sink. Hence require a close down of sink explicitly. But this is not possible when process crashes. Since when the process crashes everything within it goes away it's inherent to asynchronous sinks to have potential to loose some of the most recent logs. I don't see anything that could be done about it. The only way I can imagine to ensure that logs are guaranteed not to get lost is to use synchronous sink with some fast custom backend. Your backend could, for instance, forward logs via shared memory to some other process that actually does the writing to whichever persistent storage you choose to write to. But as far as I know there are no such off-the-shelf backends offered in Boost.Log. Cheers, Leon Do boost have any mechanism for the same (Like handling the signals of OS and like stack dumps)? What does boost prefer for unexpected termination of process where the logs will go out uncollected? Could you please help me out of this? Thanks and Regards Shaginesh PK ________________________________ Confidentiality Statement / Disclaimer : This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt. The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message. ________________________________ _______________________________________________ Boost-users mailing list Boost-users@lists.boost.orgmailto:Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users ________________________________ Confidentiality Statement / Disclaimer : This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt. The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message. ________________________________
participants (2)
-
Leon Mlakar -
Shaginesh P.K.(NeSTIT)