|
From: Dan K. <da...@ke...> - 2008-11-13 21:58:30
Attachments:
pid-opt.patch
|
I ran into a situation where I wanted to use --log-file and --trace-children=yes together. Not surprisingly, this didn't work so well. I added the following hack to cause a '$' in the log file name to be expanded to the pid. This avoids log file corruption by multiple processes writing to same file. Is there a better way to do this? Thanks, Dan |
|
From: Ashley P. <api...@co...> - 2008-11-13 22:05:50
|
On Thu, 2008-11-13 at 13:58 -0800, Dan Kegel wrote: > I ran into a situation where I wanted to use --log-file > and --trace-children=yes together. Not surprisingly, > this didn't work so well. I added the following hack > to cause a '$' in the log file name to be expanded to > the pid. This avoids log file corruption by multiple > processes writing to same file. Is there a better > way to do this? Does --log-file=log.%p do what you want? Ashley. |