Forums / Developer / error, debug and warnig.log are always cleared

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

error, debug and warnig.log are always cleared

Previous topic

Next topic

Author	Message
Sébastien Morel	Sunday 22 March 2009 7:38:46 am Hi, I have a strange behaviour with my ez 4.1, My log files is always cleared. I can have the errors by one tested url each time... Is it new and normal with 4.1 ? I read the changelog and nothing appears about this. Someone have an idea ? Thanks ++ -- eZ c'est plus fort que toi ! http://www.ez-france.org http://blog.plopix.net @Novactive (http://www.novactive.com)
Sébastien Morel	Sunday 22 March 2009 8:42:41 am After several verifications and particulary in ezdebug class. There isn't errors, the bug come from the configuration of the virtual machine( with a mount on windows (vboxfs) )..... I don't understand but fopen ($handler,'a') don't put the pointer a the end of the file..... In production environnement everything is ok and if I copy the mounted folder in another location in the VM everything is ok. My conclusion, do not use Vboxfs ! ++ -- eZ c'est plus fort que toi ! http://www.ez-france.org http://blog.plopix.net @Novactive (http://www.novactive.com)

Author

Message

Sunday 22 March 2009 7:38:46 am

Hi,

I have a strange behaviour with my ez 4.1, My log files is always cleared. I can have the errors by one tested url each time...

Is it new and normal with 4.1 ? I read the changelog and nothing appears about this.

Someone have an idea ?

Thanks
++

Sunday 22 March 2009 8:42:41 am

After several verifications and particulary in ezdebug class.

There isn't errors, the bug come from the configuration of the virtual machine( with a mount on windows (vboxfs) ).....

I don't understand but fopen ($handler,'a') don't put the pointer a the end of the file.....

In production environnement everything is ok and if I copy the mounted folder in another location in the VM everything is ok.

My conclusion, do not use Vboxfs !