On 5/9/2015 9:26 AM, Kim Alvefur wrote:
> Old thread alert!
> On 2014-06-26 03:30, deoren wrote:
>> Link to bug report if anyone is interested:
> I think you can solve this by running
> dpkg-statoverride --add syslog adm 750 /var/log/prosody
> You might also need to edit the logrotate config, if you have not done
> that already.
Thanks for the reply (old or not, replies to my posts are appreciated).
I ended up modifying my rsyslog setup to send log messages to files
outside of /var/log/prosody due to how upgrades were handled. The issue
was that rsyslog didn't have access to the files inside of /var/log/prosody.
Since then I've learned of POSIX ACLs and might give that a try sometime
to see if it's a better solution. Inertia is working against me though
(other tasks are consuming my attention now). ;)
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/prosody-dev.
For more options, visit https://groups.google.com/d/optout.