[exim-dev] [Bug 1324] Inconsistent interpretation of empty v…

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Phil Pennock
Datum:  
To: exim-dev
Betreff: [exim-dev] [Bug 1324] Inconsistent interpretation of empty values in log_file_path
------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1324




--- Comment #2 from Phil Pennock <pdp@???> 2012-12-18 22:00:33 ---
Searching "spec.txt" for "log_file_path", the very first result is describing
what the default for log_file_path is when it's unset.

Okay, it's under the -bP option description, for interrogating Exim about what
some options are set to. But then in the actual documentation for
log_file_path, the default is again described. It also says, "and section 51.1
describes how the contents of log_file_path are used". The -bP text is
slightly clearer about behaviour when unset.

When log_file_path is unset, ie "log_file_path =", files are written into a
sub-directory of the spool directory.

So: log_file_path has a default value which is equivalent to a list with an
empty item, ie use the value from build-time, and can be unset, with the
behaviour then being to use a fixed default.

Both of these are behaving as documented and no undocumented behaviour is in
play.

However, "51.1 Where the logs are written" should be more comprehensive and
pull in the description of unset from earlier, so that someone can read just
that section and understand what is intended to happen.

Patch with suggested text welcome. :)


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email