Bugs discussion

vibrokatana

New Member
poor admin, someone buy him a double strength expresso :P

make sure to check the /tmp directory, it is possible to target the apache user via uploading of files (which some php sites do to /tmp by default).
 
SELinux has targeted policies that limits the bounds by which the server can run. By doing this it can "patch" exploits easily, usually a new policy can be made as soon as the problem is detected.
 
Code:
<a href="usercp.php">ìåç á÷øä</a>
<td class="thead">äâãøåú &amp; àôùøåéåú</td>

<a class="smallfont" href="profile.php?do=editpassword">òøåê àéîééì  åñéñîà</a>
there is the problematic stuff in the user panel, if you have phpmyadmin you can do a search to try and spot the problems.

this discusess random mysql corruption http://bugs.mysql.com/bug.php?id=563

seems to be a smt problem, if furthur corruption appears we may want to bind the mysql processes to one proc.
 
Last edited:
hehe my lappy(1gb ram) never even touches the swap, my desktop(2gb) never needed one. on bootup I use barely 10% of my ram on my lappy :P
 
I dun understand any a that stuff..
But I sure am glad the Lord taught (as is continuing) to teach ya'll!

I really appreciate this forum, and I'm glad tis back up! :D

Praise Jesus! :D
 
Code:
             total       used       free     shared    buffers     cached
Mem:       1001712     435828     565884          0          4     187148
-/+ buffers/cache:     248676     753036
Swap:       524280        460     523820

thats after compiling a redicuously large program
 
Back
Top