Christian Seberino wrote:
On Wed, May 2, 2007 4:54 pm, Michael O'Keefe wrote:
regular syslog can take logs from remote machines, that feature has been
there for a long time - port 514/udp
syslog-ng uses TCP I believe which I read somewhere makes it more
agreeable to send over an encrypted channel such as stunnel. However, now
that I'm taking to you I can't see why TCP is somehow better for sending
over secure forwarded channels.
syslog-ng can use TCP, but remote syslog daemons that are configured to
forward to remote hosts prolly only use UDP.
streaming logs over TCP might remove the 1500 octet payload limit of old
syslog (prolly done to align with old MTU values, even though UDP can
handle payloads of up to 64kB with IP fragmentation)
--
Michael O'Keefe | [EMAIL PROTECTED]
Live on and Ride an 06 BMW R12GS HP2 | [EMAIL PROTECTED] / |
I like less more or less less than |Work:+1 858 845 3514 / |
more. UNIX-live it,love it,fork() it |Fax :+1 858 845 2652 /_p_|
My views are MINE ALONE, blah, blah, |Home:+1 760 788 1296 \`O'|
blah, yackety yack - don't come back |Fax :+1 858 _/_\|_,
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
