 |
 |
 |
Virtfs User Guide |  |
 |
|
This is an important configuration file that you must look through before firing up Virtfs. There are two sections to this file: the <Configuration> and <Shell Commands> sections. The <Shell Commands> section is very similar to the <Custom Template> section (as described above). This section is compromised of shell commands that virtfs will execute upon the creation of a new virtual server. You may not even need it, especially if you customised your template directory well.
The <Configuration> section is well documented and easy to follow through. For example, if you would like to change the UI program from dialog to Xdialog, you may do so under the Dialog value.
An important variable to edit (or not to) is the Leading Virtual Directory. Your template directory should be contained in this. Typically, the value of this is /virtual (your template directory would then be /virtual/template). This way, all your virtual servers will be stored in /virtual (for example, vserver.com will be in /virtual/vserver.com).
Upon starting up Virtfs you have the choice to either create a new server, or maintain an existing virtual server that you have set up before. When you choose a virtual server to configure, you can delete the server, switch on/off FTP and Mail services, add/remove users and groups, set up Apache, etc. You can even log into the virtual server as a specified user. Virtfs should help in the daily administration tasks, basically.
After setting up the networking and DNS configuration (for a virtual server), you will want to run Virtfs to set up your virtual servers. After setting them up, you may want to run Virtfs again and again to take care of the system administration for a particular virtual server.
|
|
|
Virtfs User Guide | |
|
|