Frustrating quota error

Everywhere I look for the answer to this I find incomplete threads with no resolution. If cPanel support would like to jump in I will be glad to follow instructions to figure this out.

I've got a Linode VPS running Centos 6.2 and current cPanel Release (WHM 11.30.6 (build 3) CENTOS 6.2 i686 xenpv on server). My cPanel error log is filled with this:

Code:

Tags:

Fix for file system quotas /dev/root symlink breaks

Last Updated on Saturday, 27 April 2013 03:22pm Written by spunky Saturday, 27 April 2013 03:22pm

This is a solution to a confusing problem when performing quota checks on CentOS 6.x using Linode/Xen.

When you try quotacheck you get this error:
Copy Code

root@server [~]# quotacheck -a
quotacheck: Cannot stat() mounted device /dev/root: No such file or directory

In troubleshooting the solution, you should check to see if “/dev/root” exists:
Copy Code

ll /dev/root

Tags:

CSS Content Property

CSS has a property called content. It can only be used with the pseudo elements :after and :before. It is written like a pseudo selector (with the colon), but it's called a pseudo element because it's not actually selecting anything that exists on the page but adding something new to the page. This is what it looks like:

.email-address:before {
content: "Email address: ";
}

With this CSS in place, we could have this HTML:

Tags:

Migrating a magento website

Step 1 - Create a Database

First, you need to create a new MySQL database for your store. Log in to cPanel by following the instructions given in your Account Information email. Then click on the MySQL® Database Wizard icon. Type in a name for your new database (e.g. mystore) and click Next Step (see Figure 1). Now you need to assign a new user to your database. Type in a username and password then click Next Step. Finally, check the All Privileges checkbox and click Next Step to complete the database wizard.

You can now log out of cPanel and continue with the next step.

Disable Root SSH Login on Linux

One of the biggest security holes you could open on your server is to allow directly logging in as root through ssh, because any cracker can attempt to brute force your root password and potentially get access to your system if they can figure out your password.

It’s much better to have a separate account that you regularly use and simply sudo to root when necessary. Before we begin, you should make sure that you have a regular user account and that you can su or sudo to root from it.

Tags:

How to Create a Tar GZip File from the Command Line

You’re probably familiar with making your own zip files if you’ve ever needed to transfer a group of files or if you’re managing your own backups outside of Time Machine. Using the GUI zip tools are easy and user friendly, but if you want some more advanced options with better compression you can turn to the command line to make a tar and gzip archive. The syntax will be the same in Mac OS X as it is in Linux.
Creating a Tar GZip Archive Bundle

From the command line (/Applications/Terminal/), use the following syntax:

tar -cvzf tarballname.tar.gz itemtocompress

Tags:

Pages

Subscribe to Front page feed