Re: [EXIM] Exim logging by means of syslog(3)?

[Philip Hazel]

> > Wouldn't a single configuration string list be better?
>
> Hmm. It might even be an idea to extend the meaning of log_file_path
> rather than invent a new option. It could be restricted to at most two
> components, e.g.
>
> log_file_path = syslog : /var/log/exim/%slog

That sounds good to me.

> > I like Peter Radcliffe's suggestion of continuation numbers.
>
> If I were to generate the pid myself rather than let syslog do it,
> text such as [1234.1] could be used to indicate line 1 of a
> multi-line entry from process 1234, etc. Does this sound sensible?

It does to me. As you mentioned, it also could be useful if the total
number of lines in a multiline entry is given with each of the lines.

Will these log line changes only affect the lines going to syslog? I
think that as long as it's possible, the log line format in the local
file logs should remain unchanged.

> > You're talking about calling openlog() with LOG_PID now, right?
>
> I was, but Exim could easily generate it itself.

Sure -- I just thought I'd mention the possibility. Either solution
has it's appeal, but doing _both_ would probably be a bit much :)
--
Harald