I'm not sure how the permissions get specified by rsyslog, but they were
wrong on the host I was testing with for tracking. So I'm not sure what's
going on there.

There's a play to touch edx.log into existence entirely because the mitx
rake target gather_assets fails if it's not. This particular location is
unused by everything in the world, including the rakefile, afaict.

On Mon, May 13, 2013 at 5:26 AM, jarv <notifications@github.com> wrote:

> In playbooks/roles/common/tasks/main.yml:
>
> > @@ -56,7 +56,7 @@
> >
> >  - name: Set permissions on edx log file
> >    # This is done for the benefit of the rake commands, which expect it
> > -  file: path={{log_base_dir}}/edx.log owner=syslog group=adm mode=770
> > +  file: path={{log_base_dir}}/edx.log owner=syslog group=adm mode=640
> >    tags:
>
> Is this a case where these two files {tracking,edx}.log were already in
> place with the wrong permissions?
> We should be able to let rsyslog write these with the correct permissions
> when the application starts as long as {{ log_base_dir }} is writable by
> syslog.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/edx/configuration/pull/59/files#r4191686>
> .
>