Rumi

Learn how to change the owner and group ownership of files and directories with the chown and chgrp commands. Caution: you need to do this whiled logged in as 'root' user. In order to set the ownership of a directory and all the files in that directory, you'll need the -R option: $ chown -R username somedir Here, R stands for recursive because this command will recursively change the ownership of directories and their contents. After issuing this example command, the user username will be the owner of the directory somedir, as well as every file in that directory. Tell what happens: $ chown -v username somefile changed ownership of 'somefile' to username Here, v stands for verbose. If you use the -v option, chown will list what it did (or didn't do) to the file. The verbose mode is especially useful if you change the ownership of several files at once. For example, this could happen when you do it recursively: $ chown -Rv username somedir changed ownership of 'somedir/' to username changed ownership of 'somedir/boringfile' to username changed ownership of 'somedir/somefile' to username The options of using chgrp are the same as using chown. So, for example, the -R and -v options will work with it just like they worked with chown: $ chgrp -Rv usergroup somedir changed group of 'somedir/' to usergroup changed group of 'somedir/boringfile' to usergroup changed group of 'somedir/somefile' to usergroup chown nicely reports to you what it did to each file.

In webmin >Severs > Postfix mail server > Edit config file, change this small line-

inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
#inet_interfaces = localhost

The significance is- if you don’t uncomment inet_interfaces =all, your server is completely isolated from the network. It won’t listen other than the server or localhost. In order to check if the settings are ok- you need to connect to your server from a networks pc. Open ‘cmd’ in your pc and type-

telnet X.X.X.X 25

If something returns- then its ok, else if it’s Unable to connect, you need to make the above changes I’ve mentioned.

Postfix on most systems is very nearly ready for use as the mail server for the Virtual Servers module. The only thing missing is the configuration for a virtual mapping database and, if using quotas, moving the spool directory to the same partition that user data lives on. The first can be added easily using Webmin. Browse to Postfix:Virtual Domains. Enter a type of database, and a filename for the virtual map database into the Domain mapping lookup tables field. Generally, this will be something along the lines of hash:/etc/postfix/virtual. In this example the type is a dbm hash, and the filename is virtual in the /etc/postfix directory. Save and apply your change.

Next, you’ll need to move your mail spool to the /home partition. Browse to the Postfix:Local Delivery module. Edit the Spool directory option and enter /home/mail. Save and Apply your changes.

It is useful to choose mail as the subdirectory here, because there will already exist a mail user on most systems and so there is no way to accidentally create a new user that would end up getting your mail spool as their home directory! If you don’t use Red Hat Linux, you should probably first check to be sure there is a user named mail on your system (I believe most UNIX systems do have a user of this name).

In order for POP or IMAP to work, those servers will need to know how to find the mail spool. The easiest thing to do for this is probably to create a symbolic link from /var/spool/mail to /home/mail. The command to do this:

# ln -s /home/mail /var/spool/mail

That’s it!

By default all database and data are stored in /var/lib/mysql

But whenever, you’re planning to setup a virtual hosted server, it is wise to set up and configure this db to be set up in some different bigger disk space. Like I use to place this data path to /home/mysql

How to change this using webmin

• From your webmin Servers > MySQL Database Server > MySQL Server Configuration section look for-
• Database files directory = /var/lib/mysql
• Now change this to-
  Database files directory = /home/mysql
• A small reminder- don’t forget to create “mysql” directory in /home location!
• It’s done!

You have changed the data storage path!

Precaution:
It is recommended to modify or update this mysql data path on a fresh installation- without any cpanel or virtualmin server is hosted.

And also don’t you forget to restart the MySQL service after this changes are made! Happy data organizing!!! 😛

Webmin and Usermin are simply great- but it lacks the most widely used PhpMyadmin support! However, after googling for a while I got a solution for this.

First need to download and setup the usermin module- here’s the URL for wbm package-

http://awstats.sourceforge.net/files/phpmyadmin-1.0.wbm

How to install PHPMyAdmin Module ?

• Go to Usermin > usermin Module
• insert the above URL to the text box- “From ftp or http URL”
• Click “Install module from file”. The module will be installed
• Then go Usermin > Usermin module configuration section
• Select “Mysql Database (PHPMyAdmin)”
• PHPMyAdmin URL to open- enter your full server name (default fqdn name such as http://ns4.geospacehosting.com/phpadmin)
• It’s done!

Next to configure Apache

• Go to Webmin > Servers > Apache Webserver
• Click “Default Server”
• Click “Alias and Redirects”
• In “Document Directory Aliases” section- enter From “/phpadmin” To “/etc/phpadmin”. This actually means- http://ns4.geospacehosting.com/phpadmin or any virtual hosted domain such as https://tweenpath.net/phpadmin (here tweenpath.net is the vhosted server)
• Click “Apply Changes”
• It’s done!

Most important but the core PHPMyAdmin upload and configuration

• You need to upload the PHPMyAdmin utility software package to “/etc/phpadmin”, i.e. to the target hosting server
• Open “config.inc.php” file with a text editor like emacs
• find [‘auth_type’] and enter “http” as authentication
• It’s done!