Mark == Mark Andrews [EMAIL PROTECTED] writes:
[snip]
Similarly if syslogd is using a reliable transport
to talk to another syslogd. That too can block which
will eventualy lead to blockages to applications /
memory exhaustion.
*That* is a different beast, not
I agree with Tom that the draft - at least IMHO - does not promote or
strongly encourage reliable logging.
I also agree with the observation that reliable - and blocking -
logging can cause harm to a system. However, I do not think that this
is anything that the protocol can do something
I am thinking on how to come this by on the protocol basis, but so far I
have no good clue (except that Baszi is probably right and it is a
purely operational issue). However, I know some problems in this
relation and though it is not a deadlock issue, I would like to share
the scenario for sake
