> -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Todd Michael Bushnell > Sent: Wednesday, February 02, 2011 6:40 PM > To: rsyslog-users > Subject: Re: [rsyslog] netcat (nc) utility to /dev/log not > workingwithrsyslog > > Rainer, > > I stand corrected. It turns out this does not work for sysklog or > rsyslog, but does work with syslog-ng. My apologies - I must have only > used logger with sysklog which makes sense given that I didn't need to > test large messages with sysklog; I already know it doesn't work :-) I > know from your documentation that there are some standards with which > rsyslog complies that syslog-ng does not necessarily. My need was to > test large messages against rsyslog which I now can do via network > socket so my personal emergency is over. Still, I am curious why I can > do this with syslog-ng, but not rsyslog and sysklog so the curious cat > in me will probably geek out on that for awhile to figure out why. I'm > certain I'll end up learning something along the way and will share > whatever I do learn with this email list. I searched netcat manpage > for "datagram" and got nothing. The option I use is explained like so: > > -U Specifies to use Unix Domain Sockets. > > That's not the same thing as a datagram socket so I guess syslog-ng > "takes over" /dev/log a little bit differently to do its thing than > does rsyslog and sysklog. Sorry for the misinformation and my > appreciation for your prompt and diligent assistance. Keep up the > great work.
Ah. That explains it. The story is rather simple: there are datagram and stream sockets for unix domain sockets as well. Syslog-ng, as far as I know, implements stream sockets, whereas rsyslog sticks with the standard datagram socket way of doing things. Both have pro's and con's. One result seems to be that netcat seems not to support datagram sockets (which I find surprising, but...). HTH Rainer > > Todd > > > > > On Feb 2, 2011, at 12:55 AM, Rainer Gerhards wrote: > > > Mhhh... nothing exciting, so it should work. Rsyslogd uses datagram > sockets > > on /dev/log. You use that with nc, too, right (I have no man > available right > > now).? Also, sysklogd uses datagram sockets as well... > > > > Rainer > > > >> -----Original Message----- > >> From: [email protected] [mailto:rsyslog- > >> [email protected]] On Behalf Of Todd Michael Bushnell > >> Sent: Wednesday, February 02, 2011 8:58 AM > >> To: rsyslog-users > >> Subject: Re: [rsyslog] netcat (nc) utility to /dev/log not working > >> withrsyslog > >> > >> Rainer, > >> > >> Thanks for getting back to me so swiftly. Attached is a debug from > a > >> second test system - first system was CentOS 5 box with some minor > >> config customization. This is a Fedora box with default RPM > install. > >> Same result: nothing to logs and nothing thrown in debug mode. I > tried > >> both "-c 3" as well as default backward compatibility mode. Have > not > >> yet tried throwing at network socket, but I guess I can give that a > >> shot next. Appreciate your expertise on this. > >> > >> todd > >> > >> > >> On Feb 1, 2011, at 11:24 PM, Rainer Gerhards wrote: > >> > >>> Can you provide a debug log? This sounds a bit strange... > >>> > >>>> -----Original Message----- > >>>> From: [email protected] [mailto:rsyslog- > >>>> [email protected]] On Behalf Of Todd Michael Bushnell > >>>> Sent: Wednesday, February 02, 2011 7:05 AM > >>>> To: [email protected] > >>>> Subject: [rsyslog] netcat (nc) utility to /dev/log not working > with > >>>> rsyslog > >>>> > >>>> I'm trying to transition from sysklog and initially planned on > using > >>>> syslog-ng, but have since been turned on to rsyslog. I have a > >> working > >>>> copy of syslog-ng and I routinely test sends of larger log > messages > >>>> using netcat, rather than logger, because logger has a 1024-ish > byte > >>>> message size limit. I would instead put my large message in > >> /tmp/file > >>>> and do something like this: > >>>> > >>>> nc -w0 -U /dev/log < /tmp/file > >>>> > >>>> Pretty straightforward and works fine when testing syslog or > syslog- > >> ng. > >>>> Unfortunately, it does not work with rsyslog, even though logger > >> does. > >>>> Even in debug mode, I see no response from rsyslog when I run this > >>>> command. Is there something I'm missing here? Thanks > >>>> > >>>> todd > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> 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 > > _______________________________________________ > 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
