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
Hi maintainers,
I am trying to get syslog forwarding working with a journal namespace I
created for my application.
My system is on Debian 11, systemd 247 (247.3-7+deb11u1)
Originally, my service used the default namespace and forwarding to
syslog was working. After creating a journal namespace
Hi,
Thanks for your answer.
In the meanwhile I've discovered it's linked to selinux filesystem not
mounted (don't ask me why, I'm still trying to dig into this...)
It solved most of the failed except the udev ones.
Le 26/12/2022 à 23:27, Barry a écrit :
On 26 Dec 2022, at 14:02,syst...@sio
Hi,
This is an advanced notification for an upcoming behaviour change
being considered w.r.t. user units and sandboxing options.
User units (those run by the per-user session manager) and system
units share the same configuration options. But due to differences in
privileges between the user mana
On 26.12.2022 22:56, marty leisner wrote:
I'd like to be able to run a shell before completing the pivot (I'm running
ubuntu core 20).
I'm well versed in systemV init, but not systemd.
How do I simulate the initramfs debugging methodology of "break=init" or
"break=mount" using systemd (i.e. dro
