dom@??? said:
} The only problem with this is that it's all very well massaging
} mainlog into syslog, but what does one do with things like rejectlog?
} One could specify that a differing syslog facility priority (and
} perhaps facility, too), but it would still be difficult to get the
} same level of logging that one does now, and it would all be jumbled
} together.
How about having log_file_path entry being either:-
relative/path - taken rel to spool dir
/absolute/path
@SYSLOG:facility:level
should another form of logging be added later that would have a different
@TAG
If the log_type - ie main, reject, panic (the thing that is the %s at
present) was also available as a variable expansion, the facility/level
could then be selected on log type....
Or maybe a better solution is to add a log_method tag - currently could be
set to file (default) or syslog, and then have the log_file_path
interpreted as a file or facility/level...
Lots of ways of doing these things.
One thing to watch is that some exim log lines are much too long for
syslog, and will certainly break old versions (didn't there used to be a
root exploit using this sort of thing?). Cutting syslog entries down to a
maximum length and sending long lines in several chunks will be necessary.
Doing log analysis on this trashed log format will be interesting and I
wish people luck trying it.... [especially as interleaved lines will be
quite likely as well as broken syslog entries where half the entry is
missing - you have to realise that syslog just doesn't cut it in the real
world]
Nigel.
--
[ Nigel.Metheringham@??? - Systems Software Engineer ]
[ Tel : +44 113 207 6112 Fax : +44 113 234 6065 ]
[ Real life is but a pale imitation of a Dilbert strip ]
--
*** Exim information can be found at
http://www.exim.org/ ***
