The base abstraction already allows write access to
/run/systemd/journal/dev-log but journald offers both:
- a native journal API at /run/systemd/journal/socket (see sd_journal_print(4))
- /run/systemd/journal/stdout for connecting a program's output to the journal
(see systemd-cat(1)).
In add
Hello,
Am Donnerstag, 27. April 2017, 15:39:24 CEST schrieb Jamie Strandboge:
> The base abstraction already allows write access to
> /run/systemd/journal/dev-log but journald offers both:
> - a native journal API at /run/systemd/journal/socket (see
> sd_journal_print(4)) - /run/systemd/journal/st
On Thu, 2017-04-27 at 18:31 +0200, Christian Boltz wrote:
> Hello,
>
> Am Donnerstag, 27. April 2017, 15:39:24 CEST schrieb Jamie Strandboge:
> > The base abstraction already allows write access to
> > /run/systemd/journal/dev-log but journald offers both:
> > - a native journal API at /run/system
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 k
