DASHGIR wrote:
Do you know why log4j requires to log as remote? How does it do it. IP
spoofing?
Log4j does not require to log to a remote syslog host. *You* are telling it to
log through a SyslogAppender that *you* are defining.
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexib
you can't write to Unix domain sockets (like /dev/log) from Java, so it
has to go via IP.
no IP spoofing involved: it writes to localhost (127.0.0.1), so syslog
will see the messages as coming from localhost. I know that syslog-ng has
the ability to only accept messages from certain addresses
Do you know why log4j requires to log as remote? How does it do it. IP
spoofing?
thanks
Ceki Gulcu wrote:
>
>
>
> DASHGIR wrote:
>> No error message, no output and the machine does not catch fire.
>> The hostname is indeed replaced with the machine hostname where the
>> syslog
>> daemon is
DASHGIR wrote:
No error message, no output and the machine does not catch fire.
The hostname is indeed replaced with the machine hostname where the syslog
daemon is running.
I almost assumed that the syslog is setup to accept messages from the
network. I will check with the admins.
By defaul
No error message, no output and the machine does not catch fire.
The hostname is indeed replaced with the machine hostname where the syslog
daemon is running.
I almost assumed that the syslog is setup to accept messages from the
network. I will check with the admins.
Thanks
Douglas E Wegscheid
"it does not work": no output? error message? exception? machine catches
on fire?
make sure that your syslog is set up to receive from the network (default
port udp port 514) , and not just /dev/log.
'hostname' is indeed the name of the machine running the syslog daemon?
Douglas E Wegscheid
