[syslog-ng]Running Syslog-ng chrooted
foob@return0.net
foob@return0.net
Wed, 30 May 2001 17:48:42 +0000 (GMT)
/dev/log isnt a device. its created by syslog to capture
messages that programs send to. to chroot syslog, wouldnt
you need to adjust the path and recompile all programs
that call syslog()?
sys/syslog.h:
#define _PATH_LOG "/dev/log"
If / and /usr/jail are on the same physical partition, maybe you
could hardlink.
Interested if you get anywhere with this... incidentally, is syslog
going to be running as root in the chroot? I dont suppose it
has to...
- foob
On Wed, 30 May 2001, Jon Marks wrote:
> Can you move the device file over to /usr/jail/syslog/dev/log and symlink
> it from /dev/log? That way, programs can still find it (if they don't
> care about a symlink), but it's living beneath the syslog-ng root.
>
> On Wed, May 30, 2001 at 05:52:00PM +0200, Kaladis wrote:
> > Dear Mailinglistpeoples,
> >
> > First of all I'd appreciate it if you could cc all replies to kaladis@gmx.de
> > since I'm not a member of this mailing list.
> >
> > I am trying to run syslog-ng chrooted - to be accurate, from
> > /usr/jail/syslog. I created /usr/sbin/syslog-ng, created all directories and
> > so on, copied the needed libraries etc. Syslog-ng is starting quite fine
> > within that chrooted environment as user syslog group syslog. However it is
> > not logging anything. I guess that it must have to do with /dev/log since
> > that isn't accesiable out of that environment anymore. Now I'm asking myself
> > how I could have /dev/log under /usr/jail/syslog/dev/log or what else the
> > problem could be.
> >
> > Thanks for your help
> >
> > - Kaladis
> >
> > ---
> > www.maganation.com/~kaladix - Kaladix Linux - Your Secure Linux Choice
> >
> >
> > _______________________________________________
> > syslog-ng maillist - syslog-ng@lists.balabit.hu
> > https://lists.balabit.hu/mailman/listinfo/syslog-ng
>
>