Search results

Hi Pong, thanks for the update, this bug is killing us in production, any idea what the timeline for release is?

forgot the rest of the trace from the email #8 0x00000000004fd052 in epoll::waitAndProcessEvents (this=0xb161d0, iTimeoutMilliSec=<value optimized out>) at epoll.cpp:190 #9 0x000000000049f546 in EventDispatcher::run (this=<value optimized out>) at eventdispatcher.cpp:219 #10...

Some more info: To solve another issue I upgraded from 1.3.5 to 1.3.10. I'm still getting the core file errors above in stderr.log just like before. I ran 'ls' inside /tmp/lshttpd to see what was inside bak_core lshttpd.pid lsphp5.sock lsphp5.sock.108 lsphp5.sock.172 lsphp5.sock.540...

stderr.log under usr/local/lsws/logs getting filled up with: warning: core file may not match specified executable file. warning: core file may not match specified executable file. warning: core file may not match specified executable file. warning: core file may not match specified...

If I do a fore reinstall, will I have to reconfigure my server, or will it save all my configuration setting, virtual host settings, php builds, etc?

anyone find a solution to this? same thing happens to me all the time

Example .htaccess in /regular: Options +FollowSymlinks IndexIgnore * RewriteCond %{REQUEST_URI} !^/other/all\.php RewriteCond %{REQUEST_URI} !^/other/each\.php RewriteRule ^(.*)$ standards\.php?original=$1 [QSA,R,L] Example .htaccess in /general: <Files...

So that's why it doesn't work. But any tips to make it work? I imagine porting .htaccess files into the server config is fairly common. Esp. for people on openlitespeed, which doesn't support .htaccess files. Is there some other way of accomplishing the same thing?

Trying to port my .htaccess rewrites directly into the server configuration. So on the rewrite tab of the virtual host config I went to the "Rewrite control" section and enabled rewrite. Then in the rewrite rules section I did this... <Directory [pasted path of directory containing htaccess...