one option would be for syslogd to accept network connection, but only from localhost (127.0.0.1). No worse of a security exposure than listening on the Unix socket, IMHO. This would not be a syslog,conf setting; it would need to be done with some form of firewall that would deny remote access to UDP port 514, but allow access to it from localhost.
I don't think java knows how to write to a local Unix socket (/dev/log), which is what syslogd configured with -r listens on. I have seen whisperings of a log4net syslog appender that uses native code to write to a Unix socket, see http://marc.info/?l=log4net-dev&m=109344646600810&w=2 Douglas E Wegscheid Lead Technical Analyst, Whirlpool Corporation (269)-923-5278 "A wrong note played hesitatingly is a wrong note. A wrong note played with conviction is interpretation." "Kannan Ekanath" <[EMAIL PROTECTED]> wrote on 09/19/2008 06:41:11 AM: > Hi,Log4j - 1.2.18 > I am using the Log4j Syslog Appender to write syslog messages to my > localhost. Since this is just localhost I would have expected the Appender > to not draw up any network connections. I redirect all *.info messages in my > localhost to a file and I did not see my log4j messages there. > > However, when I run the syslog daemon with the -r option (which is to accept > remote connections) I can see my log4j messages. > > My question is this, since I my sysloghost is just the "localhost", is there > a way to talk to the local syslog host without a network connection? > Apparently, our Systems folks are not okay with opening up the syslog ports > for remote connections? > > Is there an option? > > -- > Regards, > Kannan Ekanath
