INODES. The use of more than 250,000 inodes on any shared account may potentially result in a warning first, and if no action is taken future suspension. Accounts found to be exceeding the 100,000 inode limit will automatically be removed from our backup system to avoid over-usage, however databases will still be backed up. Every file (a webpage, image file, email, etc) on your account uses up 1 inode. Sites that slightly exceed our inode limits are unlikely to be suspended; however, accounts that constantly create and delete large numbers of files on a regular basis, have hundreds of thousands of files, or cause file system damage may be flagged for review and/or suspension. The primary cause of excessive inodes seems to be due to users leaving their catchall address enabled, but never checking their primary account mailbox. Over time, tens of thousands of messages (or more) build up, eventually pushing the account past our inode limit. To disable your default mailbox, login to cPanel and choose "Mail", then "Default Address", "Set Default Address", and then type in: :fail: No such user here.
INODES. Every file and directory hosted on Wildeye servers uses 1 inode and accounts considered to be using an excessive number of inodes on shared or reseller servers will be required to upgrade their hosting service or remove some of the files from their hosting service. For shared and reseller hosting services an inode count of 200,000 or more is considered excessive and is generally the result of issues within a web application or a web application configuration that is not appropriate for a shared hosting environment. We recommend maintaining less than 100,000 inodes per account for optimal performance. For VPS hosting an inode count of 4,000,000 or more is considered excessive.
INODES. The use of more than 250,000 inodes on any shared account may potentially result in a warning first and if no action is taken future suspension. Accounts found to be exceeding the 100,000 inode limit will automatically be removed from our backup system to avoid over-usage, however databases will still be backed up. Every file (a webpage, image file, email, etc) on your account uses up 1 inode. Sites that slightly exceed our inode limits are unlikely to be suspended; however, accounts that constantly create and delete large numbers of files on a regular basis, have hundreds of thousands of files, or cause file system damage may be flagged for review and/or suspension. The primary cause of excessive inodes seems to be due to users leaving their catchall address enabled, but never checking their primary account mailbox. Over time, tens of thousands of messages (or more) build up, eventually pushing the account past our inode limit. To disable your default mailbox, login to cPanel and choose "Mail", then "Default Address", "Set Default Address", and then type in: :fail: No such user here. Mail policy and limits There is a 500 hourly outgoing email limit per domain on all shared servers. This means each domain/subdomain gets its own separate 500 outgoing emails per hour limit. This limit is also applied towards mailing lists. If you send over this amount in any hour, the e- mails will fail and may bounce back with a undeliverable error. Shared servers limit each connecting IP to 30 POP checks per hour. If you go over this, you will likely get a password error indicating your login is incorrect. To fix this, just wait an hour and it will automatically unlock. To prevent this from happening, disable automatic send/receive or set a higher time interval, such as checking once every 10 minutes. Any mailing list over 500 email addresses is only allowed to be sent to during off-peak times to prevent high server loads. Off peak times qualify as all day Saturday and Sunday, and 2AM - 7AM Atlantic Standard Time, Monday through Friday.
INODES. The use of more than 50,000 inodes on any shared account may potentially result in suspension. Accounts found to be exceeding the 50,000 inode limit will automatically be removed from our backup system to avoid overusage. Every file or directory on your account uses up 1 inode. Simply exceeding the limit does not constitute grounds for suspension however accounts that constantly create and delete large numbers of files on a regular basis or causing file system damage may cause your account to be flagged for review.
INODES. The use of more than 250,000 inodes on any shared account may potentially result in a warning first, and if no action is taken future suspension. Accounts found to be exceeding the 100,000 inode limit will automatically be removed from our backup system to avoid over- usage, however databases will still be backed up. Every file (a webpage, image file, email, etc) on your account uses up 1 inode. Sites that slightly exceed our inode limits are unlikely to be suspended; however, accounts that constantly create and delete large numbers of files on a regular basis, have hundreds of thousands of files, or cause file system damage may be flagged for review and/or suspension. The primary cause of excessive inodes seems to be due to users leaving their catchall address enabled, but never checking their primary account mailbox. Over time, tens of thousands of messages (or more) build up, eventually pushing the account past our inode limit. To disable your default mailbox, login to cPanel and choose "Mail", then "Default Address", "Set Default Address", and then type in: :fail: No such user here. 7c.) Backup Limit Any shared account using more than 20 gigs of disk space will be removed from our off site weekly backup with the exception of Databases continuing to be backed up. All data will continue to be mirrored to a secondary drive which helps protect against data loss in the event of a drive failure.
