On Fri, 23.11.12 16:22, Mike (mike.almat...@gmail.com) wrote: > Hi, > > My distribution has many isolated services with his /dev/log are > disposed within the environment of isolation, for example: > /var/lib/ldap/dev/log > /var/lib/openvpn/dev/log > /var/spool/postfix/dev/log > > How to configure a journalD, which he could read such isolated sockets? > Now I see only one solution: to add the necessary sockets in > systemd-journald.socket file, but this approach is not distributive. > I would like to have the analog /etc/syslog.d which are symbolic links > to the insulated sockets or any other convenient method.
Currently, journald cannot listen on multiple syslog sockets (though we could certainly add that). A simple alternative could be to just make /var/lib/ldap/dev/log symlinks? If you are using chroots and these paths hence cannot be symlinks into the host, then it might be possible to create a new subdir somewhere in /run or so, then copy /usr/lib/systemd/system/syslog.socket to /etc/systemd/system/syslog.socket and change it there to point to a socket in this new subdir. Then, bind mount this subdir into the various chroot environment, and symlink /dev/log each time. Not pretty, but should work... Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
