Re: Guarunteed Delivery and Initial Message Submission

[by way of "Chris M. Lonvick" <[EMAIL PROTECTED]>]

 >>>>> "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 want to implement a mechanism whereby the
Mark> server can accept a number of messages before fsync()'ing, and then
Mark> ACK the last one to tell the client that all of the messages up to
Mark> that point have been received.  This obviously doesn't work for
Mark> initial message submission, because an application process needs an
Mark> ACK immediately in order to stop blocking in the library call.

Whoa! I don't want to _ever_ guarantee an fsync(). I want to be able to say
"I'm a best-efforts server, I got your message, it will be written to
non-volatile storage unless I crash". Strict delivery really should be
optional.

-- 
Carson Gaspar -- [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.cs.columbia.edu/~carson/home.html
Queen Trapped in a Butch Body