At 10:21 AM -0400 9/8/05, Daniel Senie wrote:
The code in the function vlogit() in common/logit.c explicitly does
this. I have no idea WHY it explicitly does this, but it does.
You'll find there two fprintf() calls followed by an fflush(). The
second fprintf is the issue.
Anyone know why? Should we just remove the second fprintf?
The code has been deliberately written that way for many, many years.
I always assumed it was there for better readability, but that was
just an assumption.
Personally, I don't mind it either way. I make extensive use of
logging to a separate file, and am used to the extra lines. Perhaps
a configuration file option?
At 12:58 PM -0400 9/8/05, Daniel Senie wrote:
You're sure it recompiled and you placed the new executable in
place of the old one?
I make it a habit to tweak the version or banner information when I
make a change, in order to be able to verify that I'm running the new
code. It's too easy to run the old code.
--
Randall Gellens
Opinions are personal; facts are suspect; I speak for myself only
-------------- Randomly-selected tag: ---------------
I worry that the person who thought up Muzak may be thinking up
something else.
--Lily Tomlin
