|
|||||||||||
|
Re: syslogd lsitening on per default
From: morla <morla(at)cracksucht.de>
Date: Thu Jan 31 2008 - 06:18:35 EST
even if there wanst much of a response, im back to report what i found.... maybe this will help anyone else who has a spelling problem and searches on the interwebs for an explanation. :P if you configure syslogd to log to a remote syslogserver, it will bind to port 514/UDP, even if it doesn't get the -r option passed. i find this really confusing... why would syslogd need to listen on any interface just to send data to a remote server??? makes no sense for me at all... if anybody has an idea or knows why syslogd behaves like that, it would be very interesting to hear about it on the list... (imo). regards morla
morla wrote:
-- To UNSUBSCRIBE, email to debian-security-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Thu Jan 31 06:22:57 2008 This archive was generated by hypermail 2.1.8 : Wed Mar 19 2008 - 06:55:36 EDT |
||||||||||
|
|||||||||||