In some email I received from Mark D. Roth, sie wrote:
[...]
> Please correct me if I'm misinterpretting you, but you seem to be
> saying that the verifyable delivery option should be a configurable
> parameter at the daemon level. However, it needs to be selectable at
> the API level because the user process will need the ability to select
> verifyable delivery before the message even gets to the local syslogd.
Why ? To me, every message that is sent by the local process to the local
syslogd is sent with the expectation that it will be delivered and received.
> Also, just on general principles, I think that the application code is
> in the best position to determine which behavior makes sense, because
> the system or network administrator isn't usually familiar with all
> the intricacies of the code.
So let me get this straight. The administrator configures which messages
he wants to log but he doesn't configure which of those he wants to ensure
are logged ?
It maybe that the adminstrator decides that mail.* will goto /dev/null
(i.e. not set up syslogd to receive/handle it at all) and bugger what
the application thinks it should log as "verified delivery".
Darren
