Re: Can socklog 1.0 listen on more than one socket?

Gerrit Pape <[email protected]>
Newsgroups gmane.comp.misc.pape.general
Message-ID <20060401082057.11031.qmail@cdf27c13195e1a.315fe32.mid.smarden.org>
On Mon, Mar 27, 2006 at 02:28:22PM -0700, Jeff Ross wrote:
> I've been running socklog for a long time now on OpenBSD.  Today I was 
> trying to figure out why I wasn't getting logs from the spamd process.
> 
> As it turned out, spamd runs chrooted in OpenBSD, so when spamd was trying 
> to write to /dev/log, because it was chrooted into /var/empty/ it was 
> really trying to write to /var/empty/dev/log, which didn't exist.
> 
> My first thought was to start another socklog listeing on 
> /var/empty/dev/log, and log that off to /var/log/spamd/.  That worked 
> great.
> 
> Is it possible to have socklog listen on more than one socket at 
> a time?  syslogd (at least according to the OpenBSD man page) can listen 
> to about 20 different sockets making it easy to let a chrooted process log 
> to syslog.

No, each socklog process only can listen to exactly one socket.  This
follows the design of runit's logging facility which also makes logging
of chrooted service to outside the root easy, without a socket in each
jail, but through a pipe.

Regards, Gerrit.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.