On 03/12/2015 09:02 AM, Andrei Borzenkov wrote:
I am migrating some test systems from openSUSE 11.0 to 13.2 - systemd is in fact making things quite a lot easier.
However, I have a problem with getting syslog-ng started early enough. This is probably due to a DNS problem, which will have be looked at separately. However, due to this late starting I've noticed other daemons not being able to use syslog, not even once it is started. In 13.2 standard syslog socket (/dev/log) is owned by journald which is started very early. Syslog daemons are supposed to listen on
On Thu, Mar 12, 2015 at 1:20 PM, Per Jessen <per@computer.org> wrote: private socket and journald forwards messages to syslog over this private socket. This is by design.
how is that being accomplished?
?
What exactly "other daemons not being able to use syslog" means?
Please also show syslog-ng.service definition.
E.g. openvpn - it is started quite early, so the startup messages are not logged, but later on it also does not seem to be able to log. This can't be right?
-- Per Jessen, Zürich (5.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org