human choroinic gonadotropin

Archive for January, 2011


 Powered by Max Banner Ads 

redirection usig index.html

Monday, January 17th, 2011

http://www.web-source.net/html_redirect.htm

How To Enable Security Auditing in Windows XP Pro

Saturday, January 15th, 2011

Logging events can help you monitor your computer or network and prevent a successful attack and can also prove very useful in determining how and when an attack occurred if you use the logs as forensic evidence.

  1. Click on Start
  2. Click on All Programs
  3. Click on Administrative Tools (if its there skip to Step 7. To turn it on continue with Step 4)
  4. Right-click on the Start bar and select Properties.
  5. Select the Start Menu tab and click on the Customize button
  6. Select the Advanced tab and scroll to the bottom of the options for System Administrative Tools and select the option you want
  7. Select Local Security Policy
  8. Click on the + next to Local Policies to expand the tree
  9. Select Audit Policy
  10. For each option in the right panel you can double-click on it to select Success or Failure logging
Tips:
  1. To disable logging for an option just uncheck both the Success and Failure boxes
  2. Remember that logging can affect performance. Do some research to determine the right balance between logging and performance for your system

Thank you

Mysql load

Wednesday, January 12th, 2011

to detect the user that caused mysql to be high load

mysqladmin processlist

Thank you.

mysql slow queries

Wednesday, January 12th, 2011
wget http://hackmysql.com/scripts/mysqlsla
chmod 755 mysqlsla*
mv mysqlsla* mysqlsla
./mysqlsla -lt slow /var/log/mysql-slow.log

reference 

http://forums.cpanel.net/f189/high-load-mysql-160213.html

check directory files size in linux

Sunday, January 9th, 2011

1- go inside the directory for example

cd /home/alzweac

alzweac#du -sh

2.4Gb

Thank you.

A quick performance tune for mysql – innodb_buffer_pool_size

Sunday, January 2nd, 2011

If you are using MySQL with InnoDB tables, you should really look at the innodb_buffer_pool_size.   This tells MySQL how much memory it should use to cache data on your InnoDB tables.  This cuts down on disc IO.  It can save you alot of lookup time if you are pulling out of the cache as opposed to making another call to the database table.  As a good rule of thumb this value should be set to 10% larger than the size of your database… that is assuming you have that much memory available on your server.  By default innodb_buffer_pool_size is set to 8MB.  If you have a decent sized data set, and most of you probably do, then you are going to want to increase this.  My database is about 1GB, so I set my innodb_buffer_pool_size to 2GB, so that I can account for some growth in the future.  Just be sure not to set the value too high.  If you only have 2GB of memory on your box, then don’t set it to 2GB.  This can cause paging at the OS level and that is bad news.

So here is how you set that parameter in mysql

open up your /etc/my.cnf in your favorite editor and add the parameter in the mysqld section

[mysqld]
innodb_buffer_pool_size = 2G

Then you restart mysql and the changes should be picked up.

/etc/init.d/mysqld restart

You can double check by issuing the following command in mysql client.  It will show you the variable and its value

mysql> SHOW VARIABLES;

NOW THATS A QUICK AND EASY PERFORMANCE TUNE!!

Thank you.