What steps will reproduce the problem?
1. Start a process and initialize Google logging in that.
2. Fork a child process by calling fork().
3. Have the parent and child call the LOG(INFO) simultaneously.
What is the expected output? What do you see instead?
The expectation is that glog will detect forks and have the child automatically
open a new logging file. Instead, both the parent and the child try to write to
the same file - overwriting each other's messsages.
What version of the product are you using? On what operating system?
0.3.1. Ubuntu 10.10.
Please provide any additional information below.
Please confirm if the fork'd child should call ShutdownGoogleLogging() followed
immediately by InitGoogleLogging() again to get the desired behavior. If so,
this should be documented.
Original issue reported on code.google.com by aron.sus...@nutanix.com on 22 Feb 2011 at 5:49
Original issue reported on code.google.com by
aron.sus...@nutanix.com
on 22 Feb 2011 at 5:49