On 12/12/24 13:12, Wietse Venema via Postfix-devel wrote:
syslog_name =
${multi_instance_name?{$multi_instance_name}:{postfix}}/$service_name
The main downside here is you'll end up with names such as
postfix/smtpd/smtpd but it will at least be consistent. Also we could
instead change the default itself but then we're pushing that new
default onto existing installations and I don't personally think we
should do that in this case.
Would this stutter whenever $service_name equals $process_name? For
example local/local, qmgr/qmgr, smtp/smtp, lmtp/lmtp, cleanup/cleanup,
virtual/virtual, spawn/spawn? It would be consistent, but not pretty.
Yes it would, but I'm not entirely sure that would be a downside since
it actually represents two different things that just happen to be the
same, or when the service name and command name are the same is it not
appropriate to express this? That said it is a visual glitch that I
guess a lot of people would want to avoid largely because they're not
used to seeing it that way.
We could try to eliminate stutter by making the global default a little
more complex:
syslog_name=${
multi_instance_name?{$multi_instance_name}:{postfix}
}${
{$service_name}!={$process_name}?{/$service_name}:{}
}
This should indeed work.
Unfortunately, syslog_name has the wrong name, It is a name prefix.
Right, I'm wondering if it would be appropriate to add a new setting
(not my idea it came from someone in IRC), "syslog_full_name" with a
default of:
syslog_full_name = $syslog_name/$process_name
This would give people who want it more control over the full syslog name.
I wouldn't be opposed to renaming syslog_name to syslog_prefix either.
Peter
_______________________________________________
Postfix-devel mailing list -- postfix-devel@postfix.org
To unsubscribe send an email to postfix-devel-le...@postfix.org
