On 5/9/2015 9:26 AM, Kim Alvefur wrote:
> Hi!
>
> Old thread alert!
>
>
> On 2014-06-26 03:30, deoren wrote:
>> Link to bug report if anyone is interested:
>>
>> https://code.google.com/p/lxmppd/issues/detail?id=423
>
> I think you can solve this by running
>
> dpkg-statoverride --add syslog a
Hi!
Old thread alert!
On 2014-06-26 03:30, deoren wrote:
> Link to bug report if anyone is interested:
>
> https://code.google.com/p/lxmppd/issues/detail?id=423
I think you can solve this by running
dpkg-statoverride --add syslog adm 750 /var/log/prosody
You might also need to edit the logro
On 2014-06-24 23:52, Sergei Golovan wrote:
If you look into the postinstall script inside the package you find
that the /var/log/prosody (and some other directories) permissions are
reset on upgrade unconditionally. So, I'm afraid you can't do much.
On 2014-06-25 20:21, deoren wrote:
Thanks fo
On 2014-06-24 23:52, Sergei Golovan wrote:
If you look into the postinstall script inside the package you find
that the /var/log/prosody (and some other directories) permissions are
reset on upgrade unconditionally. So, I'm afraid you can't do much.
Thanks for the feedback, I'll submit a bug r
Hi deoren,
On Wed, Jun 25, 2014 at 6:46 AM, deoren wrote:
> by prosody.im. I have this apt entry:
>
> deb http://packages.prosody.im/debian precise main
If you look into the postinstall script inside the package you find
that the /var/log/prosody (and some other directories) permissions are
On 2014-06-24 01:07, Sergei Golovan wrote:
Which operating system do you have and how did you install Prosody?
Hi Sergei,
Thanks for the reply. Sorry, I should have included that with my
original email. I'm running Ubuntu 12.04 LTS with the Debian/Ubuntu
package provided by prosody.im. I h
Hi deoren.
On Tue, Jun 24, 2014 at 5:37 AM, deoren wrote:
>
> When a package update was applied the permissions were reset to the default
> (which I think was prosody:prosody). Aside from adding the syslog user to
Which operating system do you have and how did you install Prosody?
Cheers!
--
S
> When a package update was applied the permissions were reset to the
> default (which I think was prosody:prosody). Aside from adding the
> <...>
> Thoughts?
I bet, it is distro-related issue. Not Prosody's one.
--
Best regsrds,
mva
signature.asc
Description: This is a digitally signed messa
My apologies if cross-posting between the prosody-users and prosody-dev
lists is frowned on. I'm still pretty new to using mailing lists.
---
Hi,
First of all, thanks to the devs for their work on Prosody. Really
enjoying it so far. My question is related to configuring Prosody to use
syslog
