Re: [RFC 2] logging.te: systemd-journald: loose ends

On Sunday, 9 August 2026 21:35:54 AEST Dominick Grift wrote:
> Thanks. I think the user may not have these sockets activated and that
> therefore they get created by systemd-journald instead in his
> scenario. systemd-journald itself does not seems to use
> get/setfscreatecon as it needs a type transition for io.systemd.journal
> too.
> 
> I suppose the question becomes whether refpolicy wants to support the
> scenario where the syslog socket unit is not enabled.

What is Gentoo planing to do regarding defaults for this?

It seems to me that if you are going systemd then do it properly and use the 
socket units.  Then you can restart systemd-journald without affecting 
connections.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/