------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1324
Andreas Metzler <eximusers@???> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|bug |wishlist
--- Comment #3 from Andreas Metzler <eximusers@???> 2012-12-19 19:06:26 ---
Phil Pennock wrote
> the very first result is describing what the default for log_file_path is
> when it's unset.
Imho having
log_file_path =
in the exim configuration file is not the same as "it's unset". It is set, but
to an empty value.
That documentation is easily fixable, though. I just think it is really
counterintuitive that this happens:
1) I set a smart default for log_file_path at compile time.
2) "log_file_path = " results in exim falling back to some uber-default instead
of the compile time value.
Is this argument convincing?
If it is, and if you think changing the way exim behaves does not have too big
chances to break existing systems please change it.
Otherwise, if you think the current behavior is fine (or not worth breaking
compatibility) tell me, and I will try to come up with a patch for the
documentation instead.
Thanks, cu andreas
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
