logging error

Joshua Layne joshua at willowisp.net
Thu Oct 13 22:52:57 CEST 2005


As a general note, you may not want to make this (or any file in your webroot) world-writable.
I found that the default permissions worked fine, with a

chown -R nobody:nobody logs

(and temp)... my webserver runs as nobody.

like all things open source and linux, there is no religion, only policy... one of many ways to do things.

j.
On Thu, 13 Oct 2005 22:33:53 +0200, "cappac" <cappac at capmail.info> wrote:
> 
> 
> Thanks for all tips!
> 
> This one solved my problem.
> 
> 
> ----- Original Message -----
> From: "Geuis Teses" <geuis.teses at gmail.com>
> To: dev at lists.roundcube.net
> Sent: Thursday, October 13, 2005 10:14 PM
> Subject: logging error
> 
>  I had this problem. Make sure that both files *IN* the logs directory are
>  writable.
> 
>  On 10/13/05, cappac <cappac at capmail.info> wrote:
>  >
>  >
>  >
>  > I just don't get around this error:
>  >
>  > >Warning: fopen(./logs/errors) [function.fopen] failed to create
> stream<
>  >
>  > dir logs has permission 777
>  >
>  >
>  >





More information about the Dev mailing list