Quoting Vallevand, Mark K (mark.vallev...@unisys.com): > Here is how I got syslog to work with a program running in a container. > After creating a container, do something like this: > > echo syslog setup > cat <<EOF > /etc/rsyslog.d/99-lxc-1.conf > \$AddUnixListenSocket /var/lib/lxc/container1/rootfs/dev/log > EOF > restart rsyslog > > If you are using rsyslog, of course. The rsyslog daemon only supports 100 > unix domain sockets. So, I guess that means 1 for the host /dev/log and 99 > more for containers. > > My program happily uses syslog and they end up in the host syslog.
Not sure, but I suspect you also could add a bind mount entry for /dev/log dev/log to /var/lib/lxc/container1/fstab. ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
