Date: Fri, 5 Nov 2004 09:27:17 +0000 From: David Malone <dwmalone@maths.tcd.ie> To: Makoto Matsushita <matusita@jp.FreeBSD.org> Cc: src-committers@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/syslogd syslogd.8 syslogd.c src/sys/sys syslog.h src/lib/libc/gen syslog.c Message-ID: <20041105092717.GA98184@walton.maths.tcd.ie> In-Reply-To: <20041105102609W.matusita@jp.FreeBSD.org> References: <200411042309.iA4N9v06043345@repoman.freebsd.org> <20041105102609W.matusita@jp.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 05, 2004 at 10:26:09AM +0900, Makoto Matsushita wrote: > It would be a good one, but how do I open yet another priv socket? > (Imagine you have a chroot/jail sandbox, and sshd runs inside sandbox.) libc automatically falls back to the original socket if there is no priv socket, so it shouldn't cause any problems. > Do we have yet another option, say, option -L (open priv socket), and > use it as "syslogd -l /my/jail/var/run/log -L /my/jail/var/run/logpriv" > or something like that? You can now specify the the mode for the socket on the command line, so you should be able to do: syslogd -l /my/jail/var/run/log -l 600:/my/jail/var/run/logpriv David.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041105092717.GA98184>