On Thu, 5 Aug 2010, Rainer Gerhards wrote:

> Just some more information for anyone interested. I today looked at the
> module. First of all, there is a directive to set the hostname
> ($InputUnixListenSocketHostName) but I also found out that there exist
> undocumented functionality to activate hostname parsing. In theory, this is
> done by putting a colon in front of the socket name. In practice, there seems
> to be a bug that prevents this from working at all (the colon is not
> removed). So it probably was good this was not documented ;)

so if you use a socket name that starts with a colon it should work right? 
;-)

David Lang

> I'll see that I fix that first, so that we have some basic functionality in
> place.
>
> Rainer
>
>> -----Original Message-----
>> From: [email protected] [mailto:rsyslog-
>> [email protected]] On Behalf Of Ales Kozumplik
>> Sent: Monday, August 02, 2010 1:11 PM
>> To: rsyslog-users
>> Subject: Re: [rsyslog] log forwarding through unix sockets
>>
>> On 07/30/2010 03:28 PM, Ryan Lynch wrote:
>>> I like your method, too. And thank you for mentioning 'socat', that's
>>> what gave me the idea to go in this direction, in the first place.
>>
>> Thanks. To tell you the truth at the end we found a way to forward from
>> qemu to a TCP socket, and I am happy I don't have to deal with unix
>> sockets any more.
>>
>>> Based on my own tests, I believe that 'imuxsock' and 'imudp' use
>>> different logic to parse incoming messages. 'imuxsock' always assumes
>>
>> That's exactly my feeling about this. I just think one either should be
>> able to tell every input module what format should be expected (instead
>> of letting rsyslogd try some guessing method), or that every input
>> module should by default understand a standard "officially recommended"
>> forwarding format.
>>
>> Ales
>> _______________________________________________
>> rsyslog mailing list
>> http://lists.adiscon.net/mailman/listinfo/rsyslog
>> http://www.rsyslog.com
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com
>
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to