ServerBuddies Support Blog

Enabling User/Group Quota for virtual private server that already exists.

If the virtual private server already exists, run the following command to set the parameter:

Where, 101 is the VPS ID number.

Restart the virtual private server.

Enabling User/Group Quota on a Virtual Private Server (VPS)

To enable user/group quota on a virtual private server:

Edit the configuration file to set the parameter QUOTAUGIDLIMIT that controls the second-level disk quota. The two instances when you can set the parameter is:

If you are setting the parameter before the creation of the virtual private server:

Go to the location of the virtual private server configuration file. /etc/sysconfig/vz-scripts

To enable disk quota set the value of QUOTAUGIDLIMIT to a positive value, in the configuration file. For example: QUOTAUGIDLIMIT=”150″

The default value of the parameter is zero. Setting the value of the parameter to zero disables user/group quotas.

Note: Ensure that you use this configuration file when creating the virtual private server.

Reference: http://parallels.com

If you are going to host more than 300 domains or web sites on your server, you should switch on support for piped logs in the Apache Web Server.

To enable piped logs:

Log in to the server shell.

Source from Plesk.

Enabling & Disabling suEXEC

Upon startup of Apache, it looks for the file “suexec” in the “sbin” directory (default is “/usr/local/apache/sbin/suexec”). If Apache finds a properly configured suEXEC wrapper, it will print the following message to the error log:

If you don’t see this message at server startup, the server is most likely not finding the wrapper program where it expects it, or the executable is not installed setuid root.

If you want to enable the suEXEC mechanism for the first time and an Apache server is already running you must kill and restart Apache. Restarting it with a simple HUP or USR1 signal will not be enough.

If you want to disable suEXEC you should kill and restart Apache after you have removed the “suexec” file.

Enabling Password Aging

The following example shows how password expiration can be setup for individual user accounts.

The following files and parameters in the table are used when a new account is created with the useradd command. These settings are recorded for each user account in the /etc/shadow file.

Therefore, make sure to configure the following parameters before you create any user accounts using the useradd command:

Also check - /etc/default/useradd

When a user account is created using the useradd command, the parameters listed in the above table are recorded in the /etc/shadow file in the following fields

[username]:[password]:[date]:PASS_MIN_DAYS:PASS_MAX_DAYS:PASS_WARN_AGE:INACTIVE:EXPIRE:

To create a new user account you can execute the following command:

To get password expiration information: