Am 18.08.2010 18:26, schrieb F Wolff:
>
> I think I understand your issue entirely, and I'm not sure why it is
> happening. The only ideas I can think of right now:
>
> - Complete Apache restart might be needed (not just "reload")
> - There might be a SetGID bit on the directory which influenc
Op Wo, 2010-08-18 om 18:09 +0200 skryf Johannes Ahlers:
> Hi Friedel,
>
> thank you for your quick response. The problem is, if the files are
> created with owner-read-write-only right (rw---) the Apache can't
> deliver them because he runs as user www-data which has no access to
> these fi
Am 18.08.2010 17:51, schrieb F Wolff:
> Op Wo, 2010-08-18 om 11:21 +0200 skryf Johannes Ahlers:
>
>> Hello,
>>
>> we run a Pootle server 2.1.0 with mod_wsgi on an Apache2. The Pootle
>> source code and xlif files are lying in the home directory of user
>> pootle (/home/pootle). We set the WSGI
Op Wo, 2010-08-18 om 11:21 +0200 skryf Johannes Ahlers:
> Hello,
>
> we run a Pootle server 2.1.0 with mod_wsgi on an Apache2. The Pootle
> source code and xlif files are lying in the home directory of user
> pootle (/home/pootle). We set the WSGIDaemonProcess to run under pootle
> user with u
Hello,
we run a Pootle server 2.1.0 with mod_wsgi on an Apache2. The Pootle
source code and xlif files are lying in the home directory of user
pootle (/home/pootle). We set the WSGIDaemonProcess to run under pootle
user with umask 0002. Additional the apache-user www-data is in the
pootle gro
