Date: Sat, 20 Jan 2001 21:20:39 -0800 From: "Crist J. Clark" <cjclark@reflexnet.net> To: Steve Price <sprice@hiwaay.net> Cc: current@FreeBSD.ORG Subject: Re: excessive paranoia in syslogd(8)? Message-ID: <20010120212039.M10761@rfx-216-196-73-168.users.reflex> In-Reply-To: <20010120224944.I387@bonsai.knology.net>; from sprice@hiwaay.net on Sat, Jan 20, 2001 at 10:49:44PM -0600 References: <20010120224944.I387@bonsai.knology.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 20, 2001 at 10:49:44PM -0600, Steve Price wrote: > Is it just me or does 'syslogd -s' exhibit just a little bit too > much paranoia about allowing socket connections? I was futzing > with a Perl script that needed to syslog(3) some stuff and after > much hair pulling I realized that 'syslogd -s' didn't even allow > connections from localhost. Apparently Perl opens a socket > connection to syslog and with the '-s' syslogd doesn't read from > socket connections either from localhost or from hosts specified > with -a. This is a bad thing IMHO. Either I open syslogd up to > all socket connections (including from localhost) or I can't use > syslog from Perl. You can write to the /dev/log (usually symlinked to /var/run/log) socket with '-s' set. If you want to or need to use network sockets, # syslogd -a localhost Should provide the behavior you want. As you noted this is not the same as '-s'. It is a feature and not a bug. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010120212039.M10761>