[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apparmor-dev
Subject:    Re: [apparmor] [PATCH] update base abstraction for additional journald sockets
From:       Simon McVittie <smcv () collabora ! com>
Date:       2017-04-27 18:13:41
Message-ID: 20170427181341.77lznkwnqbtbh7cd () archetype ! pseudorandom ! co ! uk
[Download RAW message or body]

On Thu, 27 Apr 2017 at 11:49:28 -0500, Jamie Strandboge wrote:
> On Thu, 2017-04-27 at 18:31 +0200, Christian Boltz wrote:
> > Is /var/run/... really needed, or is /run/... enough?
>
> It probably isn't needed, but in Ubuntu we are backporting more and more
> AppArmor to earlier releases (I don't know what other distros are doing, but it
> seemed conceivable they might do the same) and it seemed best to leave it.

As far as I'm aware, systemd pid 1 explicitly does not support any setup
other than "/run is a directory, /var/run is a symlink to /run", and
systemd-journald requires systemd pid 1.

Or does Ubuntu have some workaround to use systemd-journald in releases
older than the one in which you moved from Upstart to systemd as init?

The /run migration happened in sysvinit 2.88dsf-29 or earlier (2012)
so I would hope that any still-relevant system had this change long ago.

    S

-- 
AppArmor mailing list
AppArmor@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
[prev in list] [next in list] [prev in thread] [next in thread]