Q. Is 50,000 the inodes limit?
A: An inode is a data structure used to keep information about a file on the hosting account. The number of inodes indicates the number of files and folders the user has with them. This includes everything on the account, emails, files, folders, anything the user store on the server. The 50000 inode limit is now increased to 100000.
Shared and reseller servers only allow 100,000 files per cPanel. The user may slightly exceed this limit, but then the company will not continue to create automatic backups. It will be a TOS violation if the user continuously publish and delete large numbers of files, like 10,000 at a time.
Q. What is CPU resource usage?
A:
SHARED SERVERS
HostGator allows a maximum of 25% CPU usage limit. The user may exceed this limit for no longer than 90 seconds. It is unlikely that the user hit the 25% CPU usage unless the site script is intensive and requires more processing.
Here are some valuable tricks to lessen the CPU usage:
* Reduce the number of banners and ads from other sites.
* Avoid using too many scripts, and do not force html to handle server-side code (like php and shtml).
* Avoid using https protocol as much as possible; Encrypting and decrypting communications is noticeably more CPU-intensive than unencrypted communications.
* Flash, video, audio, and image files downloaded to the browser. This uses bandwidth only.
VPS SERVERS
The users allowed using 100% of the CPU resources. However, this is only a portion of the server’s total CPU resources. If the users are looking for more CPU resources than a Shared Server, the user will NOT want to pick VPS; instead, the user should choose a Dedicated Server.
DEDICATED SERVERS
The users are allowed using 100% of the server’s CPU resources.
A good trick for VPS and Dedicated is to turn off the webstat programs (Awstats) that comes with the cPanel. Note that AWstats and other tracking tools use CPU and MySQL connections. By turning this off, the user reduces the CPU usage.
Q. How can the user make a stronger password?
A: It is important to have a password that is easy to remember, but hard to guess. Hackers can guess the password if it is a name or word from the dictionary. The best password will contain the following:
* At least two Capital letters
* At least one lower-case letter
* At least one number
* At least two symbols
Writing down the password is the most common security risk.
However, imagining and then remembering such a password can be difficult.
Here are some tips to make stronger passwords:
1. Start with a simple word or name at least six letters long.
2. Change two letters to symbols that look similar. Use $ for s, @ for a! For i, and so on: ho$tg@tor
3. Change a letter to a number that looks similar. Use 1 for l, 0 for o, 8 for b, and so on: ho$tg@t0r
4. Include two Capital letters, like this: Ho$tG@t0r
It is acceptable to make a few different passwords and reuse them for different sites and devices. The users should not reuse the most important passwords.
Q. How can the user prevent hacking?
A: Following are some tips for preventing the hacking:
* The most important thing to do is to keep the passwords secret. If the user gives a password to someone, it needs to be sure to change it when it has done using the access. It should not write the passwords down or share them with too many people. Periodically they should change the passwords. The user can find more by searching “How can I make a stronger password?”
* Along with the same idea, the user needs to make sure that the computer does not have viruses, Trojans, key loggers, etc.
* The user should keep the scripts and downloaded programs updated. They should always upgrade to the latest version of the blog, forum, shopping cart, etc.
* The users should not have writable file permissions. The correct permissions are normally 755 or 644, and the user can check these in the File Manager. Most users know to avoid 777 permissions, but the users really want to avoid any permission settings that allow Group and World writing. (That’s anything ending in 7, 6, 3, or 2. The first number can be one of these, but not either of the last two numbers.)
Q. How does the user handle the Google Attack Page?
A: When the user sees the dreaded Google attack site warning, the user should immediately email security@hostgator.com. The user should ensure to include the domain name because the company will need to locate the virus that caused the issue and take steps to secure the account.
Note: This will only happen in Firefox because Mozilla has a relationship with Google. Google cannot actually change the website.
Once the account has cleaned and secured, please request a delisting through the Google Webmaster account. This is not something that HostGator can do for the users. The expert copies the code from Google, and gives the user step- by-step instructions to request a delisting.
http://www.google.com/support/webmasters/bin/answer.py?answer=45432
Once the user have reviewed the site and are sure it is clean, the user can submit a request for review. Note the user will need to verify site ownership before the user can request a site review.
1. Sign in to Webmaster Tools with the Google account.
2. On the Dashboard, select the site the user want.
3. On the Overview page, click Request a review and follow the instructions.