they have 777 permisions but who owned the content of that directory???

I just don't get around this error:

...

Warning: fopen(./logs/errors) [function.fopen] failed to create stream<

dir logs has permission 777

Yes, but what permissions does the file errors in logs have? It already existed in the tarball I downloaded.

Just a thought.

On Thu, 2005-10-13 at 21:56 +0200, cappac wrote:

I just don't get around this error:

...

Warning: fopen(./logs/errors) [function.fopen] failed to create stream<

dir logs has permission 777

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@capmail.info wrote:

Thanks for all tips!

This one solved my problem.

----- Original Message ----- From: "Geuis Teses" geuis.teses@gmail.com To: dev@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@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