[systemd-devel] Systemd-219: Failed to start Create Volatile...
ric.prog at gmail.com
Tue Mar 3 19:27:56 PST 2015
Thanks for the reply;)
RICARDO BASTOS CAMPOS
Análise e Desenvolvimento de Sistemas
MS Researcher at INF in Parallel and Distributed Processing Systems
Porto Alegre, RS - Brasil
2015-03-03 14:50 GMT-03:00 Zbigniew Jędrzejewski-Szmek <zbyszek at in.waw.pl>:
> On Mon, Mar 02, 2015 at 05:07:40PM -0300, RicΛrdo Bastos™ wrote:
> > Hi all,
> > I'm using this tip to solve problem in systemd-TMPFILES-setup.service:
> > <
> > So I commented the following lines in systemd.conf file:
> > # a+ /var/log/journal/%m - - - - d:group:adm:r-x,d:group:wheel:r-x
> > # A+ /var/log/journal/%m - - - - group:adm:r-x,group:wheel:r-x
> > Now the service is starting correctly :)
> > *# **Active: active (exited) since Seg 2015-03-02 13:37:04 BRT; 3h 1min
> You get the warning most likely because the filesystem that
> /var/log/journal or /run/log/journal are on does not support ACL. So
> users in the wheel and adm groups will not be given access to the
> journal through ACLs.
> This isn't really a problem — apart from the unsightly warning in the
> logs, and the missing access, this should not have any other effects.
> I pushed a commit to reduce the warning to debug level if the fs
> does not support ACLs.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the systemd-devel