(Note: This message discusses some implementation details of the new
syslog on a Unix system, but only in as much as it relates to protocol
design issues.)
The general mode that we've been using for discussing the new syslog
protocol is the transfer of logs from one machine to another. In this
On Wed Oct 27 05:12 1999 +1000, Darren Reed wrote:
In some email I received from Mark D. Roth, sie wrote:
[...]
I agree that best-effort is good enough for the default, especially if
TCP is used for the new protocol. However, if we're going to provide
a guarunteed/verifyable
On Wed Oct 27 05:07 1999 +1000, Darren Reed wrote:
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.
In some email I received from Mark D. Roth, sie wrote:
[...]
I agree that best-effort is good enough for the default, especially if
TCP is used for the new protocol. However, if we're going to provide
a guarunteed/verifyable delivery option, we need to ensure that the
data will not be
On Tue Oct 26 13:21 1999 -0400, [EMAIL PROTECTED] wrote:
"Mark" == Mark D Roth [EMAIL PROTECTED] writes:
Mark Another possible difference between syslogd-syslogd transfers and
Mark process-syslogd transfers is the fsync() interval. Since the
Mark receiving syslogd cannot send an ACK
Hi Mark,
I'd change the title to "Verifiable Delivery" rather than "Guaranteed
Delivery" and propose that it be expanded a bit more. The sender can
either decide if it wants to verify that the delivery was successful,
or that is does not care if the mesages were received.
This can address
"Mark" == Mark D Roth [EMAIL PROTECTED] writes:
Mark Another possible difference between syslogd-syslogd transfers and
Mark process-syslogd transfers is the fsync() interval. Since the
Mark receiving syslogd cannot send an ACK until it's fsync()'ed its queue
Mark file(s), we will probably
