8 reputation
5
bio website nixtalks.net
location Kherson, Ukraine
age
visits member for 1 year, 8 months
seen Sep 26 at 16:15

Oct
28
awarded  Popular Question
Sep
26
awarded  Scholar
Sep
26
accepted APCu and APC setting unclear
Jun
25
awarded  Student
May
1
comment APCu and APC setting unclear
@Tallboy Seems apc support has been dropped in php 5.5. Now APC bundled in php 5.5 core.
Mar
18
asked APCu and APC setting unclear
Sep
28
comment Apache - Return 404 for all execept selected
Hope I found what i need. This works for me if below block inserted in httpd.conf context <Directory /usr/local/www/apache22/data/*/wp-admin> RewriteCond %{REMOTE_ADDR} !^77\.120\.9\.3$ RewriteRule . google.com/404.php [R=404,L] </Directory> I saw this in Rewrite redirects examples and adapted to serve 404 error, but initially it was intended to do redirection.
Sep
26
comment Disable php functions per website
Know this way. But want to keep one user for simplicity and as far i know fastcgi works slower than mod_php
Sep
26
asked Disable php functions per website
Sep
26
asked Apache child died for unknown reason
Sep
26
comment Apache - Return 404 for all execept selected
I mentioned in question already where i have added rules. Sure restarted apache, mod_rewrite loaded pastebin.com/b65GhsVZ and working fine as plenty of my website using it. Regarding moving wp-admin, sure i can use bash script to rename all in one shot, but i'm curious (and actually going to use) how to accomplish this without touching core files.
Sep
26
revised Apache - Return 404 for all execept selected
added 1 characters in body
Sep
26
comment Apache - Return 404 for all execept selected
I have been awaiting for such reply. The reason is to obfuscate bad bots trying to guess presence of Wordpress installed. So if they get 404 error then they won't try to explore for wordpress vulnerabilities.
Sep
25
asked Apache - Return 404 for all execept selected
Sep
12
comment One unix socket for all php-fpm pools
See i have some experience in setting nginx as frontend and apache as backend on one server and in such case i may chroot every website in apache vhost config using basedir value and moreover i may adjust similiar to nginx's "pm.*" apache's StartServers, MinSpareThreads, MaxSpareThreads, ThreadLimit, ThreadsPerChild, MaxClients, MaxRequestsPerChild values and they will be applied for all websites.
Sep
12
awarded  Editor
Sep
12
revised One unix socket for all php-fpm pools
edited body
Sep
12
comment One unix socket for all php-fpm pools
That's i afraid the most, so sad. Let's assume i may live without per website logs and same time need to chroot each website. Is anything could I try ? I never tried these following options, maybe they can help -; ;chroot = ;chdir = /var/www
Sep
12
comment One unix socket for all php-fpm pools
Because i guess this is only way to separate php scripts by using php_admin_value[open_basedir] value. That means if one website hacked, they can't move up and infect others. Another thing is per website logs. If it possible, could you please share such config with one pool ?
Sep
12
asked One unix socket for all php-fpm pools