Each namespace has its own journald service instance, in this case
systemd-journald@my-namespace.service, and each such instance has been
programmed to build the runtime directory name from the specified instance
name. So the new journald process that handles "my-instance" uses
/run/systemd/journal
I found a minimal solution, which I don't quite understand.
I ended up creating an rsyslog config at /etc/rsyslog.d/my-namespace.conf
with the content:
input(type="imuxsock" Socket="/run/systemd/journal.my-namespace/syslog")
I guess with this rsyslog manages the socket, creating it if it doesn't
The easiest way might be to just symlink it from the existing socket with
`ln -s ../journal/syslog /run/systemd/journal.my-namespace`... other than
that, depends on the syslog daemon, e.g. an additional unix-stream() for
syslog-ng or imuxsock for rsyslogd. (The socket for the main namespace is
set
/run/systemd/journal/syslog exists and I am sure that ForwardToSyslog=yes
is set on the default namespace.
I’d like to setup an additional socket at
/run/systemd/journal.my-namespace/syslog to forward logs to syslog from my
own namespace. Can you point me to the documentation for how I should do
t
The forwarding itself is namespaced. ForwardToSyslog relies on the syslogd
daemon setting up a receiving socket at /run/systemd/journal/syslog through
which journald will send the messages – but for namespaced journald, the
runtime directory is different (the point of it being namespaced) so the
sy
