Silicon Technix

As we all know that the Firefox browser takes a lot of our computer memory, this is of course made a slow computer performance and also affect our activity on the internet.

Why does this happen? One main cause is because Firefox itself. Although popular, it seems that Firefox is not a lightweight browser. This browser is quite fat and wasteful, because it spent a fairly high computer resource. For the first time you run it this browser (version 2) spends at least 10 mega memory in Linux, and 20 mega in Windows. The more you open tabs / web then spent the greater memory and the CPU busies all you work. Read the rest of this entry »

If you are using CPanel with VPS and getting Quota errors.
OK here is the solution for VPS.
Please try following:

1- First change the /etc/fstab file similar to as follows:

# This file is edited by fstab-sync - see 'man fstab-sync' for details
LABEL=/ / ext3,usrquota defaults 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmps defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
LABEL=SWAP-sda2 swap swap defaults 0 0

2- change in the

/etc/sysconfig/vz-scripts/xxx.conf

setup it to QUOTAUGIDLIMIT="3000"
reboot

3- this command as well as in sequence :

quotaoff -av
quotaon -av
/scripts/fixquotas

it should solve the issue

1) If you wish to limit the total number of recipients in an email, you can do that using the variable:

smtpd_recipient_limit=10

# postconf -e 'smtpd_recipient_limit=10'

# /etc/init.d/postfix restart

2) If you wish to specifically limit the number if recipients in TO and CC. You can do that with the option in main.cf:

header_checks = regexp:/etc/postfix/header_checks

contents of /etc/postfix/header_checks

/^To:([^@]*@){50,}/ REJECT Sorry, your message has too many recepients.
/^Cc:([^@]*@){50,}/ REJECT Sorry, your message has too many recepients.

This will not work for BCC. By the time the message gets to header_checks, the BCC header will be already removed.

Oracle 11g sets by default password expiration. The expired message needs to re-login and reset the old password to new one.

Suppose you have an user with the status “expired”:

You can check that by: Read the rest of this entry »

There is a worldwide, highly-distributed WordPress attack that is ongoing on most of the WordPress powered blogs.

The following steps can be used to secure (by password protection) wp-login.php for all WordPress sites in your cPanel account:
How to Password Protect the wp-login.php File
There are two (2) steps in accomplishing this. First you need to define a password in the .wpadmin file, and then you activate the security in the .htaccess file. Read the rest of this entry »