В Thu, 12 Mar 2015 13:46:55 -0400 Ruben <ruben.safir@my.liu.edu> пишет:
On 03/12/2015 01:09 PM, Andrei Borzenkov wrote:
В Thu, 12 Mar 2015 11:56:47 -0400 Ruben Safir <ruben.safir@my.liu.edu> пишет:
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?
"Syslog daemons are supposed to listen on
private socket and journald forwards messages to syslog over this private socket. "
how are you getting systemd to start on "private sockets", whatever that is?
Sorry, I do not see any occurrence of word "systemd" in what I wrote so I do not understand your question. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org