From: Francis Cianfrocca Date: 2006-06-02T20:24:31+09:00 Subject: Re: syslog lib/module for remote logging ------=_Part_6785_24794646.1149247235834 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline remote syslog works on UDP. If you want to use TCP, you're not going to use syslog. Two options: 1) examine how likely your system is to drop packets. UDP usually drops packets in the kernel (either your computers or your routers) when the network stack is congested or busy- it's easy to write a test program that will make it happen, but quite rare in many local networks. (Over the Internet, forget it.) 2) Use a reliable message-queuein= g system of some kind. On 6/2/06, Pe=F1a, Botp wrote: > > fr Park: > # You can try something like this: > # > # require 'socket' > # require 'win32/eventlog' > # include Win32 > # > # syslog_dest =3D 13 > # syslog_port =3D 514 > # syslog_server =3D '192.168.123.122' > # > # s =3D UDPSocket.new > # EventLog.open('Application').tail{ |log| > # message =3D "WinEventLog > # #{log.time_generated.asctime}||#{log.event_type}||#{log.source > # }||#{log.computer}||#{log.user}||#{log.description}" > # s.send("<#{syslog_dest}>#{message}",0,syslog_server,syslog_port) > # } > > Sweet. > But the udp just reminded that i'm sending security logs that i do _not > want to miss. > > Do you know of any syslog-like module that uses tcp? Is this possible > using a drb-like framework? > > kind regards -botp > > ------=_Part_6785_24794646.1149247235834--